Provider Alias not part of Schema Anymore
See original GitHub issueIn Terrastack (~ a month ago) the provider alias
attribute was part of the Schema. Now it’s missing from the AWS provider schema. Wondering if that change was intentional.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Help! Provider aliases no longer working since .14 - Terraform
My use case is defining multiple accounts or regions in provider blocks, then calling them as aliases to deploy modules. Terraform Provider ......
Read more >Missing provider error when using alias · Issue #26312 - GitHub
We finally found the issue. We have a call to a module where an additional provider was set but was not declared in...
Read more >The multi-part identifier could not be bound - Stack Overflow
In my case the issue turned out to be the alias name I had given to the table. "oa" seems to be not...
Read more >How to Create Service Aliases and Mark Services as Private
Deprecating Service Aliases. If you decide to deprecate the use of a service alias (because it is outdated or you decided not to...
Read more >Unable to connect to SQL named instance using alias name
(provider: Named Pipes Provider, error: 40 - Could not open a ... there are two nodes – one for 32 bit aliases and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, got it 👍
Then
alias
is now more like a meta attribute in providers, similar tocount
in resources, I assume.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’ve 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.