Switch back to user-provided IAM key for Floaty #80
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
simu
force-pushed
the
revert-floaty-iam
branch
3 times, most recently
from
1ef9efb
to
3d0241d
Compare
3 tasks
bastjan
approved these changes
Jul 7, 2023
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.
Exoscale's new IAM API (v3) isn't yet supported by the Terraform module, so we switch back to a user-provided IAM key for Floaty
This reverts #69 (commit c693867), reversing changes made to 10e07d4.
This PR also updates the Exoscale Terraform provider to v0.50.0, since we've updated the provider in the vshn-lbaas-exoscale module as well.
See https://github.com/appuio/terraform-modules/releases/tag/v5.0.0
Replaces #81 #76
Checklist
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog