-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(upgrade): upgrading aws-provider and fixing warnings #179
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
candonov
requested review from
nabuskey,
vara-bonthu,
nimakaviani and
csantanapr
as code owners
March 25, 2024 16:08
csantanapr
approved these changes
Mar 25, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @candonov !
johnphilips3
pushed a commit
to johnphilips3/crossplane-on-eks
that referenced
this pull request
Mar 25, 2024
* fixing some warnings * matching service * reverting a test * feat(upgrade): upbound aws-provider to 1.2.1 and clearing warnings * upgrading eksclt as well * apigw warning cleanup
candonov
added a commit
that referenced
this pull request
Mar 25, 2024
…#177) * Eksctl update (#2) * Update package version and args to match terraform bootstrap * Add deployment for crossplane helm provider and argocd to eksctl bootstrap * temporary change to region for testing with existing deployment in us-west-2 * Adjust permission boundary to allow CreateRole Quotes around ACCOUNT_ID in environmentconfig * Change region to us-east-1 to match default in terraform bootstrap Remove Deny for CreateRole Add missing ControllerConfig apply for Helm Provider * Request changes from PR Review * Install ArgoCD chart from cli instead of via crossplane helm provider * S3 secret fix (#4) * Add annotations to for saving s3 bucket as secret for s3irsa example * Add writeConnectionSecretToRef to base.spec in Composition Change writeConnectionSecretToRef.name in claim in case of conflicts * Add annotations for ConnectionSecret to s3irsa composition * use secret for bucketname * corrected connectiondetails * change secret key to match configmap remove configmap * feat(upgrade): upgrading aws-provider and fixing warnings (#179) * fixing some warnings * matching service * reverting a test * feat(upgrade): upbound aws-provider to 1.2.1 and clearing warnings * upgrading eksclt as well * apigw warning cleanup * Update CODEOWNERS (#180) Adding Navya to Codeowners * Resolving merge conflicts Eksctl update (#2) * Update package version and args to match terraform bootstrap * Add deployment for crossplane helm provider and argocd to eksctl bootstrap * temporary change to region for testing with existing deployment in us-west-2 * Adjust permission boundary to allow CreateRole Quotes around ACCOUNT_ID in environmentconfig * Change region to us-east-1 to match default in terraform bootstrap Remove Deny for CreateRole Add missing ControllerConfig apply for Helm Provider * Merge conflicts fix Request changes from PR Review * Install ArgoCD chart from cli instead of via crossplane helm provider * Merge conflict fix S3 secret fix (#4) * Add annotations to for saving s3 bucket as secret for s3irsa example * Add writeConnectionSecretToRef to base.spec in Composition Change writeConnectionSecretToRef.name in claim in case of conflicts * Add annotations for ConnectionSecret to s3irsa composition * use secret for bucketname * corrected connectiondetails * change secret key to match configmap remove configmap * Resolve merge conflict for provider version * Resolve merge confict * Resolve merge conflict - add cr --------- Co-authored-by: candonov <25967713+candonov@users.noreply.github.com>
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.
What does this PR do?
Upgrading upbound-aws-provider to v1.2.1 and clearing related warnings
Motivation
Housekeeping
More
Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
Yes, I have added a new example under examples to support my PR
Yes, I have updated the docs for this feature
Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)
Note:
For Moderators
Additional Notes