fix(eks-v2-alpha): ensure kubectl provider and handler functions use the same vpc configuration#34878
fix(eks-v2-alpha): ensure kubectl provider and handler functions use the same vpc configuration#34878
Conversation
|
Exemption Request: No functional change to express in an integration test |
ebfe321 to
6edc85b
Compare
vishaalmehrishi
left a comment
There was a problem hiding this comment.
Nice catch, thank you for the fix!
|
Re integration tests: I think it would be good to update existing tests/add new tests which verify that the provider and handler lambdas are set up using the same VPC configuration. |
db0b136 to
6b84e80
Compare
6b84e80 to
65ea7d8
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing To prevent automatic closure:
This PR will automatically close in 14 days if no action is taken. |
|
Hi @msessa ! |
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
|
Closing in favor of #36735. This is the same patch with updated snapshots. |
|
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
Closes #34877
Reason for this change
The kubectl
ProviderfunctionVpcConfigshould match theHandlerfunction.Description of changes
vpcconstruct is passed to bothHandlerandProviderDescription of how you validated changes
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license