-
Notifications
You must be signed in to change notification settings - Fork 19
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
Implement Helm storage backend logic #650
Labels
Milestone
Comments
mszostok
changed the title
Helm Runner [builtin: 3MD / external: 8MD]
Implement Helm storage backend logic
Mar 1, 2022
Proposed subtasks: Setup [2MD] (no dependencies)It can be further split into two tasks, but I don't think it makes sense to do so. The most important thing is that the point no 1 needs to be done ASAP to unblock other subtasks.
Helm release backend implementation [1MD] (dependency: Setup/1)
Helm template backend implementation [2MD] (dependency: Setup/1)
Storage usage [3MD] (dependency: Setup)
Documentation [1MD] (dependency: Setup) |
This was referenced Mar 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Blocked By: #645
As the Helm backend storage and allow its discovery and consumption via dedicated TypeInstance.
Subtasks
AC
The Helm storage backend consists of two quite independent parts:
Helm release storage
/cmd/helm-storage-backend
. Implement gRPC server. Types are already generated.backend.context
to allow specifying it.GetValue
method, the rest just validate data (e.g. onDelete checks whether a given Helm release).Helm template storage
A storage backend that supports helm templating:
- In context: go template + helm release name + namespace
Common
- RemoveAs discussed with @mszostok, we'll keep it to have it as a support for further workflow stepsoutput.goTemplate
.- Stop supporting usage of funcs fromAs discussed with @mszostok, we'll keep it to have it as a support for further workflow steps_helpers.tpl
storage backend
section:Related issues
See epic #604 for the reason and use cases.
The text was updated successfully, but these errors were encountered: