Skip to content

Support multiple external IPs for services in blueprint tables - #11131

Draft
bnaecker wants to merge 1 commit into
ben/multiple-eips-in-inventory-typesfrom
ben/multiple-eips-in-database-blueprints
Draft

Support multiple external IPs for services in blueprint tables#11131
bnaecker wants to merge 1 commit into
ben/multiple-eips-in-inventory-typesfrom
ben/multiple-eips-in-database-blueprints

Conversation

@bnaecker

Copy link
Copy Markdown
Collaborator
  • Add a child table of the main blueprint zone, which stores the external IPs for each zone. This supports multiple addresses, each with a reference back to the owning zone.
  • Add schema migration and test for the data migration portion of it
  • Add test ensuring we currently fail when storing more than one IP for a zone into the new table. This preserves current behavior, since the planner only generates <= 1 IP per zone today.

- Add a child table of the main blueprint zone, which stores the
  external IPs for each zone. This supports multiple addresses, each
  with a reference back to the owning zone.
- Add schema migration and test for the data migration portion of it
- Add test ensuring we currently _fail_ when storing more than one IP
  for a zone into the new table. This preserves current behavior, since
  the planner only generates <= 1 IP per zone today.
@bnaecker
bnaecker marked this pull request as draft August 21, 2026 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant