Suggestion to handle 'required' resources or default resources created in new Twilio accounts with less friction #123
Labels
status: waiting for feature
feature will be implemented in the future
type: twilio enhancement
feature request on Twilio's roadmap
Issue Summary
Twilio accounts have some resources that are required, and are created as part of a new account, but are not recognised automatically as part of terraform. Some of these appear to be just defaults to get you started, but others appear to be required and have a special status.
For example, one of the serverless services is required and should not be removed, and Flex only uses the 'default' versions of some components, like Chat or Conversations services
In order to handle this, we have had to employ workarounds to import these resources when we create new accounts:
https://github.com/techmatters/flex-plugins/blob/master/scripts/src/terraformSupplemental/importDefaultTwilioResourcesToTerraform.ts
However this isn't a foolproof solution, and it has been a source of significant headaches when the default resources created by new accounts change.
Ideally we should be able to work with newly created Twilio accounts via the terraform provider without having to import resources first, and should thereafter know which versions of resources are required or special versions from their Terraform configuration, rather than it having to be tracked separately
Suggested Change
default = true
for a default conversations service.twilio_default_serverless_service_config_v1
, and only have thetwilio_serverless_services_v1
used for creating additional serverless servicesThe text was updated successfully, but these errors were encountered: