Fix provider schema matching #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aeschright
approved these changes
Mar 16, 2021
radeksimko
force-pushed
the
fix-alias-ref-decoding
branch
from
978b5f8 to
e89b919
Compare
radeksimko
force-pushed
the
fix-alias-ref-decoding
branch
from
e89b919 to
ec1c685
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on hashicorp/hcl-lang#25
This fixes a bug which affects some configurations where resource or data source names do not carry the prefix of the provider, and/or where aliases are used.
hashicorp/hcl-lang#25 has an example and further explanation of the bug.
It is possible that most users never noticed this problem, but I ran into it when implementing #26