Update the provider's documentation regarding the apikey and secretkey #42
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.
The documentation (both on https://github.com/DNSMadeEasy/terraform-provider-dme and https://registry.terraform.io/providers/DNSMadeEasy/dme/latest/docs) does not provide the information regarding the
DME_API_KEYandDME_SECRET_KEY. As with most providers, secrets can be provided with the environment variables but it is not documented anywhere.Additionally, if you search the closed issues, you can see outdated mentions to
apikeyandsecretkeyin this issue. The new variables names were added with this PRFinally there was a broken image link (I used the wayback machine to see what it looked like in the past) and I used the logos from the HashiCorp Brand website. Some minor whitespace fixes are in there too.