Provide a way to "stub" the Terraform provider #51766
Labels
feature-request
Used for new features in Teleport, improvements to current should be #enhancements
terraform-provider
Issues relating to the Teleport Terraform provider in the teleport-plugins repo
ux
What would you like Teleport to do?
Some Terraform deployment stacks require providers to be declared globally whether they are used as part of the specific module or not.
Teleport's Terraform provider does not currently allow itself to be "stubbed" i.e. used without a valid cluster address and identity file - it requires an
addr
andidentity
to be specified in the provider configuration and will attempt to ping them on initialization.Trying to provide Teleport with a bogus
addr
(localhost
) andidentity
(/dev/null
) causes the provider's startup to fail with an error that it cannot decode the identity file.We should provide a way to stub/dry-run the provider so that it doesn't try to do anything on startup if it isn't required.
What problem does this solve?
Easier deployment into existing customer architectures.
If a workaround exists, please include it.
None currently known.
The text was updated successfully, but these errors were encountered: