Skip to content
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
merged 6 commits into from
Mar 25, 2024

Conversation

candonov
Copy link
Contributor

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:

  • Not all the PRs require examples and docs
  • We prefer small, well tested pull requests. Please ensure your pull requests are self-contained, and commits are squashed

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

Copy link
Member

@csantanapr csantanapr left a 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 !

@csantanapr csantanapr merged commit 26fcb45 into awslabs:main Mar 25, 2024
1 check passed
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants