feat(dbdr/net-peering) Add commands to configure net peerings of DB-DR

[leo-scalingo]

• database-network-configuration: Get networking information on a database to create a net peering
• database-net-peerings: List all net peerings
• database-net-peerings-add: Create a net peering to the database based on an outscale net peering request
• database-net-peerings-remove: Delete a netpeering
• database-endpoints: List the different types of endpoints of a given database (public/private rw/ro access)

• Add a changelog entry in the section "To Be Released" of CHANGELOG.md

[notion-workspace]

🗒️ [FEAT] For DB-DR, multiple endpoints should be manageable (public/net-peering/rw/ro etc.)

[curzolapierre]

Could you add example of output in PR's description please?

One question but overall LGTM

[curzolapierre]

Question Why not using already exported helper from detect/app.go?

[leo-scalingo]

The existing helper aimed at loading app + addon + database behind the DB. Here the new endpoints are DBFCC, we don't need the addon or anything, it's simply /databases/:id/network_configuration for instance, while before we were loading the addon, the hitting the db-api with the addon uuid. It's not required for these endpoints.

[curzolapierre]

Indeed, and it's currently the only one DBFCC endpoint, right?

[leo-scalingo]

Yes :-)

[briceamen]

LGTM

[curzolapierre]

LGTM

[curzolapierre]

Indeed, and it's currently the only one DBFCC endpoint, right?

[leo-scalingo]

@curzolapierre

└> scalingo database-create --type postgresql-ng --plan postgresql-dr-starter-4096 --ip-range 10.244.0.0/24 test-net-peering-1
-----> Your postgresql-ng database 6a2ab4130da2d1fe69f12345 ('test-net-peering-1') is being provisioned…

└> scalingo databases
┌──────────────────────────┬────────────────────┬───────────────┬────────────────────────────┬───────┬─────────┬─────────┐
│            ID            │        NAME        │     TYPE      │            PLAN            │ ROLE  │ STATUS  │ PROJECT │
├──────────────────────────┼────────────────────┼───────────────┼────────────────────────────┼───────┼─────────┼─────────┤
│ 6a2ab4130da2d1fe69f12345 │ test-net-peering-1 │ postgresql-ng │ postgresql-dr-starter-4096 │ owner │ running │ default │
└──────────────────────────┴────────────────────┴───────────────┴────────────────────────────┴───────┴─────────┴─────────┘

└> scalingo --database test-net-peering-1 database-network-configuration     
┌─────────────────────┬─────────────────┐
│ Outscale account ID │ 5667276334223    │
│ Outscale net ID     │ vpc-43245325    │
│ IP range            │ 10.100.255.0/24 │
└─────────────────────┴─────────────────┘

└> scalingo --database test-net-peering-1 database-net-peerings-add --outscale-net-peering-id pcx-09016123
-----> Net peering '2f482307-12d7-4606-b411-1653baf868aa' creation has been initiated for database 'test-net-peering-1'.
  /!\  Expect some delay for the net peering to be applied.

└> scalingo --database test-net-peering-1 database-firewall-rules-add --cidr 10.100.4.192/26 --label 'DBDR 1'         
-----> Firewall rule '08019731-b069-4c03-b77a-d11f3f13f0f3' has been added to database 'test-net-peering-1'.
  /!\  Expect some delay for the firewall rules to be applied.

Connect to the private Outscale VPC

$ ping 10.100.255.13
PING 10.100.255.13 (10.100.255.13) 56(84) bytes of data.
64 bytes from 10.100.255.13: icmp_seq=2139 ttl=62 time=0.833 ms
64 bytes from 10.100.255.13: icmp_seq=2140 ttl=62 time=0.557 ms
64 bytes from 10.100.255.13: icmp_seq=2141 ttl=62 time=0.518 ms
64 bytes from 10.100.255.13: icmp_seq=2142 ttl=62 time=0.571 ms
64 bytes from 10.100.255.13: icmp_seq=2143 ttl=62 time=0.539 ms
64 bytes from 10.100.255.13: icmp_seq=2144 ttl=62 time=0.581 ms
64 bytes from 10.100.255.13: icmp_seq=2145 ttl=62 time=0.571 ms
64 bytes from 10.100.255.13: icmp_seq=2146 ttl=62 time=0.664 ms
64 bytes from 10.100.255.13: icmp_seq=2147 ttl=62 time=0.660 ms
64 bytes from 10.100.255.13: icmp_seq=2148 ttl=62 time=0.600 ms