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

Enable Triggers to create custom non-Tekton resources #1696

Closed
GijsvanDulmen opened this issue Feb 17, 2024 · 4 comments · Fixed by #1699
Closed

Enable Triggers to create custom non-Tekton resources #1696

GijsvanDulmen opened this issue Feb 17, 2024 · 4 comments · Fixed by #1699
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@GijsvanDulmen
Copy link
Contributor

Feature request

It would be great if it was configurable for Tekton Triggers to create custom resources instead of only Tekton resources.
I understand it's not useful for everybody and maybe shouldn't be the default, but in a lot of use cases it does improves the plugin nature of Tekton Triggers.

Use case

In our case we wanted to use K8qu to create a "Queued" PipelineRun. This involves creating a custom QueueJob resource which creates the PipelineRun. But in other use cases I can imagine you sometimes also want to create K8s Jobs to trigger based on something sent into the EventListener.

@GijsvanDulmen GijsvanDulmen added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 17, 2024
@savitaashture
Copy link
Contributor

WG discussion:

During call we discussed that we can enable this feature and creation of resources can be enabled based on the SA permissions

@GijsvanDulmen
Copy link
Contributor Author

@savitaashture That sounds like a really nice addition to triggers! Is there any help needed for implementing it?

@savitaashture
Copy link
Contributor

Hi @GijsvanDulmen
Definitely would you like to contribute ?

@GijsvanDulmen
Copy link
Contributor Author

Yes, I will go and see if I can create PR for it.

@dibyom dibyom linked a pull request Feb 23, 2024 that will close this issue
7 tasks
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
None yet
Development

Successfully merging a pull request may close this issue.

2 participants