nicolai86 / awesome-codepipeline-ci Goto Github PK

Instead of compiling the github oauth token into the plugin it would be more secure to place it inside KMS and then resolving this at runtime. This also allows for easier secret rotation if the need arises.

Hello!! this is an awesome project and it's great to have a smart workaround for the short comings of AWS Codepipeline.

Feel free to close this issue if the code already supports this workflow, but I am looking for something specific:
My company has decided on Gitflow, which requires the creation of 'release candidate' branches when code from 'develop' is deemed ready for release. Currently, I have to hardcode the release candidate branches name into our pipelines, which isn't ideal and will not scale well. I was hoping that AWS Codepipeline would support a wildcard feature where I can target for any branch that starts with 'release/', but of course, AWS doesn't support this.
Is it possible to implement a feature into this that looks for any new branch created that matches a certain regex pattern? (as opposed to any new PRs)

Thank you!!

Would you consider adding a license file to this project? This would be consistent with good community practices and would allow others to build upon your work with a clear set of rules for what is acceptable.

For maximum compatibility with other free software projects, please consider using MIT license, such as expressed here:

https://opensource.org/licenses/MIT

(replace the copyright statement with your copyright, of course)

Hey @nicolai86 with this approach do you get charged $1 per pipeline? Or because your bringing them down before the 30 day window, you don't get charged?