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

[FEATURE] Deploy Triggers with Operator #240

Open
1 task done
adambkaplan opened this issue Feb 5, 2025 · 1 comment
Open
1 task done

[FEATURE] Deploy Triggers with Operator #240

adambkaplan opened this issue Feb 5, 2025 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@adambkaplan
Copy link
Member

Is there an existing feature request for this?

  • I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

Shipwright's operator should install Triggers once there is a release.

Describe the solution that you would like.

Operator should install Triggers, with its configuration tunable by a CRD.

Describe alternatives you have considered.

No response

Anything else?

No response

@adambkaplan adambkaplan added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 5, 2025
@adambkaplan adambkaplan added this to the release-v0.15.0 milestone Feb 5, 2025
@adambkaplan adambkaplan changed the title [FEATURE] Deploy Triggers v0.15.0 [FEATURE] Deploy Triggers with Operator Feb 20, 2025
@adambkaplan
Copy link
Member Author

Moivng this as a candidate to v0.16.0. We want to release Triggers with v0.15.0, however this hasn't happened yet and will put the operator release at risk of missing the deadline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Todo
Development

No branches or pull requests

1 participant