You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'd like to programmatically integrate a droplet configured as an internet gateway with k8s-staticroute-operator. I believe it'd be generally useful information and would possibly move progress along towards automatically provisioned internet gateways being a thing on Digital Ocean if droplet metadata, specifically the initial droplet gateway was accessible through terraform.
Describe the solution you'd like
Ideally, a metadata or some appropriately named attribute be returned from the digitalocean_droplet resource and data sources, which contains at least the droplet's configured gateway.
Describe alternatives you've considered
Adding an init-script or similar field to the digitalocean_kubernetes_node_pool arguments for initial node configuration.
The text was updated successfully, but these errors were encountered:
tlowerison
changed the title
Include droplet metadata in digitalocean_droplet resource and data returned attributes
Include droplet gateway metadata in digitalocean_droplet resource and data returned attributes
Dec 20, 2023
Thanks for the suggestion. I definitely see how this would be useful. Though I'm not sure it is something we can accommodate in Terraform at the moment. The Droplet metadata API is only accessible from the Droplet itself. We'd need the information to be included in the public API.
Using a remote-exec provisioner, you could access the metadata API, but there is not currently an officially supported way to export data from a provisioner. Unfortunately this is not something HashiCorp is prioritizing: hashicorp/terraform#610
There is an interesting third-party SSH provider that I've seen used to achieve something similar:
i was looking over the api usage in this codebase and noticed that network is available which has some useful information, including gateway. the addition of the network data would be super useful and was also requested here.
any chance if this making it into the terraform provider?
Is your feature request related to a problem? Please describe.
I'd like to programmatically integrate a droplet configured as an internet gateway with k8s-staticroute-operator. I believe it'd be generally useful information and would possibly move progress along towards automatically provisioned internet gateways being a thing on Digital Ocean if droplet metadata, specifically the initial droplet gateway was accessible through terraform.
Describe the solution you'd like
Ideally, a
metadata
or some appropriately named attribute be returned from thedigitalocean_droplet
resource and data sources, which contains at least the droplet's configured gateway.Describe alternatives you've considered
Adding an
init-script
or similar field to thedigitalocean_kubernetes_node_pool
arguments for initial node configuration.The text was updated successfully, but these errors were encountered: