We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When executing a CI build (step branch-deploy), one can see that the function configuration is updated:
branch-deploy
https://app.circleci.com/pipelines/github/adobe/helix-s3r2-sync/575/workflows/988a84ff-7b27-4d21-b046-c8a4b2ca50ff/jobs/1257
Look for the line:
updating existing Lambda function configuration helix-services--s3r2-sync
in code this happens here:
helix-deploy/src/deploy/AWSDeployer.js
Line 267 in 04c455a
I think this causes newly started function invocations of the main function to use that CI configuration, which is unexpected.
main
cc: @stefan-guggisberg
The text was updated successfully, but these errors were encountered:
let's consider this as a known issue and document it.
Sorry, something went wrong.
No branches or pull requests
When executing a CI build (step
branch-deploy
), one can see that the function configuration is updated:https://app.circleci.com/pipelines/github/adobe/helix-s3r2-sync/575/workflows/988a84ff-7b27-4d21-b046-c8a4b2ca50ff/jobs/1257
Look for the line:
in code this happens here:
helix-deploy/src/deploy/AWSDeployer.js
Line 267 in 04c455a
I think this causes newly started function invocations of the
main
function to use that CI configuration, which is unexpected.cc: @stefan-guggisberg
The text was updated successfully, but these errors were encountered: