-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support standalone triggers #84
Comments
As of #39 (comment) standalone triggers are planned (in an upcoming minor release — However, there is no need for an attachment resource. Your proposal is probably inspired by IAM policy attachments, but really, the trigger just needs a pipeline ID and that's it. |
## What * Add resource for Pipeline Cron Trigger * Fix Terraform Acceptance tests * Add Acceptance Tests to CI * Add release automation (release drafter, labeler, automatic changelog drafting) * GH Repo best practices (PULL_REQUEST_TEMPLATE, CODEOWNERS, etc) * Misc documentation fixes ## Why * Only git triggers are currently supported. * Triggers should be a standalone resource. The next minor release (`0.2.0`) will support remaining standalone triggers (registry, helm, git). ## Notes * Closes #39 * Closes #88 * #84 Co-authored-by: Yonatan Koren <10080107+korenyoni@users.noreply.github.com> Co-authored-by: korenyoni <korenyoni@users.noreply.github.com>
Please see #39 (comment) Unfortunately the API used for these standalone triggers is being deprecated and we are moving towards inline blocks for them instead 😞 |
Hi,
Is there any chance we might see support for pipeline triggers that are defined outside of the
codefresh_pipeline
block?Being able to do something like this would be wonderful:
Cheers
The text was updated successfully, but these errors were encountered: