Introduce named templates #55
Labels
enhancement
New feature or request
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
This issue is stale because it has been open for 180 days with no activity. |
|
Keep open |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the operator uses a single template for all deployments (
templateDeployment.yaml). While users may customize this template (see #49) we might have the situation where different app-definitions may require slightly different templates. We should provide a way to contribute different templates and map app definitions to their template.The text was updated successfully, but these errors were encountered: