twilio / terraform-provider-twilio

Terraform Twilio provider
MIT License
63 stars 13 forks source link

Featiure Request: Add domain output variable to serverless environment resource #85

Open stephenhand opened 2 years ago

stephenhand commented 2 years ago

Issue Summary

Observed in provider v0.9.2

Currently the twilio_serverless_services_environments_v1 doesn't expose the serverless domain as an output variable. This means on the terraform plan I am building, we have to resort to manual workarounds to use this domain setting up other resources, it would be nice if we could just take it straight from the serverless environment resource

https://github.com/twilio/terraform-provider-twilio/tree/main/twilio/resources/serverless/v1#twilio_serverless_services_environments_v1

Code Snippet

resource "twilio_serverless_services_environments_v1" "my_environment" {
  service_sid = twilio_serverless_services_v1.my_serverless.sid
  unique_name = "my_environment"
  domain_suffix = "my_environment"
}

...

resource "other_resource_type" "my_resource" {
  twilio_serverless_domain = twilio_serverless_services_environments_v1.my_environment.domain
}
eshanholtz commented 2 years ago

This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog. (Reference ID: DI-1790)

janorivera commented 2 years ago

@eshanholtz Hi!, I was wondering if this bug was fixed ? if not, how can I track its evolution?

GPaoloni commented 2 years ago

Is this a work in progress? Is there a ETA?

janorivera commented 2 years ago

hey @GPaoloni! we should write them a monthly message until someone pick this up :D

robert-bo-davis commented 1 year ago

We have hacked around the issue by using an external data provider that loads the data using the python twilio client.

But, in the long run, it would probably make sense for the twilio provider to increase the amount of output that it provides after creating resources or to provide its own data resources to prevent users from having to write their own data resources using the same APIs that the provider is leveraging behind the scenes.