Skip to content
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

Open
pdpol opened this issue Oct 24, 2024 · 3 comments · May be fixed by #2275
Open

codepipeline::OutputArtifacts does not support Files property #2274

pdpol opened this issue Oct 24, 2024 · 3 comments · May be fixed by #2275

Comments

@pdpol
Copy link

pdpol commented Oct 24, 2024

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?

@markpeek markpeek linked a pull request Oct 24, 2024 that will close this issue
@markpeek
Copy link
Member

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.

@pdpol
Copy link
Author

pdpol commented Oct 24, 2024

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.

@pdpol
Copy link
Author

pdpol commented Oct 24, 2024

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:

Resource handler returned message: "The following action cannot contain a commands field: BuildAction. To use the commands field, use a compute action. (Service: CodePipeline, Status Code: 400, Request ID: 6f0ba7ae-68a2-4a9d-a49d-93a840952ec0)" (RequestToken: 35247562-9ed4-d609-0f30-d0f6a30a0193, HandlerErrorCode: GeneralServiceException)

Removing the Files property managed to fix it, so I think there's probably something I'm not understanding about the purpose of that property or how it works that is both causing the error and potentially also not required for my purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants