-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
codepipeline::OutputArtifacts does not support Files property #2274
Comments
The Files property is missing from the resource specification so troposphere doesn't know about it. I did patch it in via PR #2275. You can pull that branch to see if it is actually implemented in CloudFormation. |
Thank you @markpeek! I was able to successfully generate a valid yaml template with the patch. I am now running into unrelated errors in CloudFormation that I'll have to figure out but this does appear to add the proper support. |
Unfortunately it appears the error I got may actually be related. Essentially, I had a working build stage with a single action that I wanted to add an output artifact to as well as a subsequent test stage with an input artifact that references it. While I was able to generate a template with the patch, updating my stack resulted in this error:
Removing the |
I'm putting together a CodePipeline stack and found that the
OutputArtifacts
class does not support the documented Files property.Is this a known issue, and are there known workarounds to supplying the path of artifacts in a build action that I need to access in the next stage?
The text was updated successfully, but these errors were encountered: