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

Easy way to provide custom values.schema.json files for Helm Charts #3535

Closed
GeKasap opened this issue Oct 1, 2021 · 1 comment · Fixed by #5530
Closed

Easy way to provide custom values.schema.json files for Helm Charts #3535

GeKasap opened this issue Oct 1, 2021 · 1 comment · Fixed by #5530
Assignees
Labels
component/ui Issue related to kubeapps UI kind/feature An issue that reports a feature (approved) to be implemented
Milestone

Comments

@GeKasap
Copy link

GeKasap commented Oct 1, 2021

Description:

This is not an issue, rather than a nice-to-have.

Currently, Kubeapps reads the values.schema.json file, from the helm chart. There are some public charts, without such file, or one that I (as a final user) want to modify according to my needs.

Workaround for this is to customize the helm chart only to add my custom file, publish it to a chart repo like Harbor (and deploy it if needed), and add this custom Harbor to my kubeapps.

Would be very nice, if we could overwrite this file, either during deploy or by providing a repo, dedicated only for such files, with some predefined structure.

@antgamdia antgamdia added this to the Form refactor milestone Oct 1, 2021
@antgamdia antgamdia added component/ui Issue related to kubeapps UI kind/feature An issue that reports a feature (approved) to be implemented priority/low labels Oct 1, 2021
@ppbaena ppbaena added this to Kubeapps Mar 9, 2022
@ppbaena ppbaena moved this to 🗂. Backlog in Kubeapps Mar 9, 2022
@ppbaena ppbaena added this to Kubeapps Mar 31, 2022
@ppbaena ppbaena moved this to 🗂 Backlog in Kubeapps Mar 31, 2022
@ppbaena
Copy link
Collaborator

ppbaena commented Jun 9, 2022

Need to think about this as the Bitnami charts could potentially remove the current values.schema.json used for simple forms in Kubeapps.

@ppbaena ppbaena added the next-iteration Issues to be discussed in planning session label Jun 9, 2022
@ppbaena ppbaena removed the next-iteration Issues to be discussed in planning session label Aug 29, 2022
@ppbaena ppbaena added the next-iteration Issues to be discussed in planning session label Oct 6, 2022
@ppbaena ppbaena moved this from 🗂 Backlog to 🗒 Todo in Kubeapps Oct 10, 2022
@antgamdia antgamdia moved this from 🗒 Todo to 🏗 In Progress in Kubeapps Oct 19, 2022
@antgamdia antgamdia moved this from 🏗 In Progress to 🔎 In Review in Kubeapps Oct 20, 2022
antgamdia added a commit that referenced this issue Oct 24, 2022
### Description of the change

Once each of the PRs of the series related to [this
milestone](https://github.com/vmware-tanzu/kubeapps/milestone/27) has
been merged, this final one is adding/fixing the test cases: adding new
ones for the functionality we've added and fixing others. Besides, some
minor fixes have been added (which have been discovered with the unit
tests :P)

### Benefits

Tests will pass now.

### Possible drawbacks

N/A

### Applicable issues

- related #3535

### Additional information

> **Note**
> This PR is part of a series of PRs aimed at closing [this
milestone](https://github.com/vmware-tanzu/kubeapps/milestone/27).
>  PR 6 out of 6


Edit: existing e2e tests are also failing :S, will have a look at them
next week.

Signed-off-by: Antonio Gamez Diaz <[email protected]>
antgamdia added a commit that referenced this issue Oct 26, 2022
### Description of the change

As per the discussion in
#5530, this PR is adding a
`featureFlags.schemaEditor` flag to enable the schema editor for those
users who really want it.

### Benefits

The schema editor will be available, but only if really needed.

### Possible drawbacks

It is a work-in-progress feature until we also save the schema or use in
the backend.

### Applicable issues

- related #3535 

### Additional information

I've fixed some typos here as well.

Signed-off-by: Antonio Gamez Diaz <[email protected]>
antgamdia added a commit that referenced this issue Oct 26, 2022
### Description of the change

The basic forms view has been recently revamped with plain JSON schema
support. However, most of the charts (and maybe other packages) do not
bring any schema file as part of their bundle.

#3535 brings some ideas on how to solve it, but, this PR is just paving
the way with a very simplistic approach: let users edit/add a schema
from a text editor.

Currently, there is no way to upload a file externally, but if this
happens to be helpful, could be added in a follow-up PR.

### Benefits

Users will be able to edit/add json schemas for improving the "basic
form" experience (validations, defaults, etc...).

### Possible drawbacks

Important: this "edited (or added)" schema is NOT being used on the
backend side. Meaning you can't expect a proper validation or any
further schema enforcement. Using the schema in the backend as well
would imply some extra changes that could be performed in a follow-up PR
if really needed.

### Applicable issues

- fixes #3535

### Additional information

> **Note**
> This PR is part of a series of PRs aimed at closing [this
milestone](https://github.com/vmware-tanzu/kubeapps/milestone/27). I
have split the changes to ease the review process, but as there are many
interrelated changes, the tests will be performed in a separate PR (on
top of the branch containing all the changes).
>  PR 1 out of 6


![PR-1](https://user-images.githubusercontent.com/11535726/197021211-e64814a7-29b1-4ac7-8043-51075f9dda9d.gif)

Signed-off-by: Antonio Gamez Diaz <[email protected]>
Repository owner moved this from 🗂. Backlog to ✅. Done in Kubeapps Oct 26, 2022
Repository owner moved this from 🔎 In Review to ✅ Done in Kubeapps Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/ui Issue related to kubeapps UI kind/feature An issue that reports a feature (approved) to be implemented
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants