-
Notifications
You must be signed in to change notification settings - Fork 224
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
S3 ETL fails when "Build: enabled: False #318
Milestone
Comments
I'm working on a fix for this problem, will update once it is ready. |
sbkok
added a commit
to sbkok/aws-deployment-framework
that referenced
this issue
Mar 3, 2021
…sabled **Why?** When the build stage is disabled, the deploy stages incorrectly tried to use the build output artifact. These should use the source artifact instead. **Linked issues** * awslabs#236 * awslabs#318
sbkok
added a commit
to sbkok/aws-deployment-framework
that referenced
this issue
Mar 3, 2021
**Fixes 🐞** * Fixes `timeout` and `environment_variables` to be used when defined in the default CodeBuild Deployment provider properties awslabs#307, closes awslabs#306. * Fixes intrinsic functions for account_region param files awslabs#333, closes awslabs#147. * Fixes use of deployment from source directly when build stage is disabled awslabs#334, closes awslabs#236 and closes awslabs#318.
Merged
sbkok
added a commit
that referenced
this issue
Mar 3, 2021
**Fixes 🐞** * Fixes `timeout` and `environment_variables` to be used when defined in the default CodeBuild Deployment provider properties #307, closes #306. * Fixes intrinsic functions for account_region param files #333, closes #147. * Fixes use of deployment from source directly when build stage is disabled #334, closes #236 and closes #318.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An example such as the following fails because the source output artifact doesn't match the deploy input artifact. I've provided the solution in this ticket.
S3 output artifact is "output-source".
When Build is set to "enabled: false", CodeBuild is skipped and the S3 deploy's input artifact is "{0}-build".format(self.map_params['name']
The generated CloudFormation for the pipeline fails with a complaint that there isn't an output format for "{0}-build".
Solution: Add a build the following block when building the Deploy action after the initial set block..
The text was updated successfully, but these errors were encountered: