fix: added datadog provider source to avoid conflicts #254
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
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.
📝 Description
11:54:41 Error: Failed to query available provider packages
11:54:41
11:54:41 Could not retrieve the list of available versions for provider
11:54:41 hashicorp/datadog: provider registry registry.terraform.io does not have a
11:54:41 provider named registry.terraform.io/hashicorp/datadog
11:54:41
11:54:41 Did you intend to use datadog/datadog? If so, you must specify that source
11:54:41 address in each module which requires that provider. To see which modules are
11:54:41 currently depending on hashicorp/datadog, run the following command:
11:54:41 terraform providers
🔗 Related Issues