Skip to content

feat: add private attribute to instance_pool resource#489

Open
mdnix wants to merge 1 commit into
exoscale:masterfrom
mdnix:master
Open

feat: add private attribute to instance_pool resource#489
mdnix wants to merge 1 commit into
exoscale:masterfrom
mdnix:master

Conversation

@mdnix

@mdnix mdnix commented Jan 26, 2026

Copy link
Copy Markdown

Description

We bootstrap our infrastructure via this provider and need private instance pools. The option was available in the web UI and API but not exposed in this provider.

I added the private attribute to exoscale_instance_pool resource to support creating instance pools without public IP addresses. This matches the existing behavior of exoscale_compute_instance.

resource "exoscale_instance_pool" "workers" {
  # ...
  private = true
}

Checklist

  • Changelog updated (under Unreleased block)
  • Acceptance tests OK
  • For a new resource, datasource or new attributes: acceptance test added/updated

Testing

Tested locally with OpenTofu using dev_overrides in ~/.tofurc - successfully created a private instance pool

@mdnix

mdnix commented Feb 20, 2026

Copy link
Copy Markdown
Author

any input here would be great

@kobajagi

kobajagi commented Apr 8, 2026

Copy link
Copy Markdown
Contributor

Thanks for contribution. UX vise i am leaning toward adding a new attribute public-ip instead (done already in cli). As is private is in conflict with ipv6_address and should be marked as such.

Anyway this feature is on our roadmap, once we internally decide on the approach we may base on your PR so I'll keep it open for a bit longer. Thanks again.

@mdnix

mdnix commented Apr 14, 2026

Copy link
Copy Markdown
Author

Thanks for contribution. UX vise i am leaning toward adding a new attribute public-ip instead (done already in cli). As is private is in conflict with ipv6_address and should be marked as such.

Anyway this feature is on our roadmap, once we internally decide on the approach we may base on your PR so I'll keep it open for a bit longer. Thanks again.

Thanks for the update. Glad this is on the roadmap. Happy to help out here

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.

2 participants