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

Support dynamic template selection #118

Open
bobh66 opened this issue Aug 31, 2024 · 0 comments
Open

Support dynamic template selection #118

bobh66 opened this issue Aug 31, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@bobh66
Copy link
Contributor

bobh66 commented Aug 31, 2024

What problem are you facing?

I have a need to use different templates for the same composition depending on user input. The existing implementation only supports a hard-coded template name reference which must be specified when the Composition is created.

How could this Function help solve your problem?

Allow for the template name to be determined based on content of the composite resource, similar to the discussion in crossplane/crossplane#5906

This could mean specifying a template name from a composite field source, or using dynamic label selection to select a configmap template based on label keys and values, where the values could also come from the composite.

@bobh66 bobh66 added the enhancement New feature or request label Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant