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

Allow more flexibility in the code which converts CR to Helm values #113

Closed
porridge opened this issue Nov 9, 2021 · 0 comments · Fixed by #114
Closed

Allow more flexibility in the code which converts CR to Helm values #113

porridge opened this issue Nov 9, 2021 · 0 comments · Fixed by #114
Assignees
Milestone

Comments

@porridge
Copy link
Member

porridge commented Nov 9, 2021

As a developer of an operator, I would like to have more flexibility in the code which converts a custom resource object to the helm chartutil.Values. Currently such code needs to conform to the values.Mapper interface which simply maps chartutil.Values to another chartutil.Values, which is just map[string]interface{}, and does not allow returning errors.

Specifically the desired features are:

  • ability to leverage Go type checking and IDE code inspection capabilities, by operating on typed API structs, rather than shapeless tree of string -> interface{}. This would be possible if the interface would accept an Unstructured which then can be converted into a typed struct.
  • ability to reach out to the cluster to fetch other resources possibly referenced by the CR, and propagate context information as well as errors properly

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants