Problem
Creating prerequisite resources for a NICo site currently requires several REST API calls that must be made in the right order. Operators need to create or verify resources such as provider, tenant, site, IP blocks, allocations or allocation constraints, VPCs, VPC prefixes, instance types, and instances.
This flow is too easy to get wrong because the required objects are distributed across multiple API calls and identifiers from earlier calls must be carried into later ones.
Requested improvement
Provide a guided or declarative workflow for creating site prerequisite resources.
The workflow should:
- Initialize provider and tenant if needed.
- Create or verify site resources.
- Create IP blocks and allocation-related resources.
- Create VPCs and VPC prefixes.
- Create or verify instance types.
- Optionally allocate instances when machines are ready.
- Be idempotent where possible.
- Emit a replayable manifest of created resource IDs.
Why this matters
Site bring-up should not depend on operators manually stitching together many REST calls. A guided workflow would reduce operator error and make recovery/recreate flows much easier.
Possible shape
A command or declarative input such as:
nico-admin site bootstrap --file site-prereqs.yaml
or an API endpoint that accepts a single site prerequisite bundle and returns a manifest of created or existing resources.
Problem
Creating prerequisite resources for a NICo site currently requires several REST API calls that must be made in the right order. Operators need to create or verify resources such as provider, tenant, site, IP blocks, allocations or allocation constraints, VPCs, VPC prefixes, instance types, and instances.
This flow is too easy to get wrong because the required objects are distributed across multiple API calls and identifiers from earlier calls must be carried into later ones.
Requested improvement
Provide a guided or declarative workflow for creating site prerequisite resources.
The workflow should:
Why this matters
Site bring-up should not depend on operators manually stitching together many REST calls. A guided workflow would reduce operator error and make recovery/recreate flows much easier.
Possible shape
A command or declarative input such as:
or an API endpoint that accepts a single site prerequisite bundle and returns a manifest of created or existing resources.