Fix: update quickstart azure provider version #735
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
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
loomkoom
force-pushed
the
pr/az-prov-ver
branch
from
b9ad960
to
1c1a84a
Compare
|
Thanks for the version bump, can you make the same changes in |
The azure provider version in quickstart is several versions behind, which resulted in incompatibility when using current upbound docs (eg. Client Certificate authentication). Signed-off-by: loomkoom <[email protected]>
loomkoom
force-pushed
the
pr/az-prov-ver
branch
from
1c1a84a
to
cb3c504
Compare
|
I added the change to |
plumbis
approved these changes
Mar 21, 2024
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.
I was following the Azure quickstart docs but had trouble getting it to work.
The error I got was the following:
Which seemed like an issue with Terraform after some superficial searching but not too sure what was going on.
I was using client certificates for authorization and after looking at the provider versioning realized that this was only introduced in v0.40.0 and the version in the docs was way behind.
After using the latest version everything worked fine.