-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
chore(codepipeline-actions): bump up the solutionStack in the integ test #28799
Conversation
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
…bump-solution-stack-version
Pull request has been modified.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…est (#28799) Currently, the solutionStack of Elastic Beanstalk that is specified is out of date, causing integ tests to fail. ``` "No Solution Stack named '64bit Amazon Linux 2023 v6.0.2 running Node.js 18' found. (Service: ElasticBeanstalk, Status Code: 400, Request ID: 625a591c-9bb2-4c7c-9404-cf192fdae9bb)" ``` It may be better in the future that integ-test can always deploy using the latest version using the custom resource. (It may be difficult to use AwsCustomResource because the size of the `SolutionStacks` (array) property alone is 4KB.) https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-elastic-beanstalk/Interface/ListAvailableSolutionStacksResultMessage/ ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…est (#28799) Currently, the solutionStack of Elastic Beanstalk that is specified is out of date, causing integ tests to fail. ``` "No Solution Stack named '64bit Amazon Linux 2023 v6.0.2 running Node.js 18' found. (Service: ElasticBeanstalk, Status Code: 400, Request ID: 625a591c-9bb2-4c7c-9404-cf192fdae9bb)" ``` It may be better in the future that integ-test can always deploy using the latest version using the custom resource. (It may be difficult to use AwsCustomResource because the size of the `SolutionStacks` (array) property alone is 4KB.) https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-elastic-beanstalk/Interface/ListAvailableSolutionStacksResultMessage/ ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Currently, the solutionStack of Elastic Beanstalk that is specified is out of date, causing integ tests to fail.
It may be better in the future that integ-test can always deploy using the latest version using the custom resource.
(It may be difficult to use AwsCustomResource because the size of the
SolutionStacks
(array) property alone is 4KB.)https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-elastic-beanstalk/Interface/ListAvailableSolutionStacksResultMessage/
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license