Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log warning for unmatched configuration providers #27757

Closed
knutwannheden opened this issue Feb 12, 2021 · 2 comments
Closed

Log warning for unmatched configuration providers #27757

knutwannheden opened this issue Feb 12, 2021 · 2 comments
Labels
enhancement new new issue not yet triaged

Comments

@knutwannheden
Copy link

Current Terraform Version

0.14.6

Use-cases

When using a module the user can specify providers to be used by the module using aliases and which the module has declared proxy configuration blocks for. In case a provider is specified for which no matching (by alias) proxy configuration block exists in the module, it would be helpful if Terraform would log a warning. This can happen in a number of situations:

  • there is a typo in the alias on the consumer side
  • the provider alias on the module side was changed or the provider proxy was even removed
  • the module inadvertently changed the proxy configuration block in a regular configuration block (e.g. by adding an empty features block)

Attempted Solutions

Proposal

As described under Use-cases I think it would make sense if the terraform command could log warnings when the configured providers don't align with the module's provider proxy configurations.

References

@knutwannheden knutwannheden added enhancement new new issue not yet triaged labels Feb 12, 2021
@jbardin
Copy link
Member

jbardin commented Feb 12, 2021

Thanks @knutwannheden!
Closed by #27739

@jbardin jbardin closed this as completed Feb 12, 2021
@ghost
Copy link

ghost commented Mar 15, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement new new issue not yet triaged
Projects
None yet
Development

No branches or pull requests

2 participants