-
Notifications
You must be signed in to change notification settings - Fork 706
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
SchemaEditor behind a feature flag #5564
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1417,20 +1417,24 @@ clusters: | |
- name: default | ||
domain: cluster.local | ||
|
||
## @skip featureFlags Feature flags (used to switch on development features) | ||
## | ||
featureFlags: | ||
## @param featureFlags.operators Enable ingress record generation for Kubeapps | ||
## | ||
operators: false | ||
|
||
## RBAC configuration | ||
## | ||
rbac: | ||
## @param rbac.create Specifies whether RBAC resources should be created | ||
## | ||
create: true | ||
|
||
## @section Feature flags | ||
|
||
## Used enable some opt-in development features | ||
## | ||
featureFlags: | ||
## @param featureFlags.operators Enable support for Operators in Kubeapps | ||
operators: false | ||
## @param featureFlags.schemaEditor Enable a visual editor for customizing the package schemas | ||
## | ||
schemaEditor: false | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fine either way, just wondering if there may be other options for the schemaEditor in the future. If so, we may want to give it structure ( There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Mmm, good point. I don't know, perhaps yes, there might be more options, but this would mean this feature is no longer "in development", but is something more "stable". There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh sorry - I wasn't proposing moving it from But fine either way, it's in development anyway :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ahhh, got it, got it. I didn't get your point :P Then, yes, it could be a good idea; I can perform the changes in the main #5530 PR |
||
|
||
## @section Database Parameters | ||
|
||
## PostgreSQL chart configuration | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,7 +28,7 @@ const { | |
const namespace = clusters[currentCluster].currentNamespace; | ||
|
||
let spyOnUseDispatch: jest.SpyInstance; | ||
const kubeaActions = { ...actions.kube }; | ||
const kubeActions = { ...actions.kube }; | ||
beforeEach(() => { | ||
actions.repos = { | ||
...actions.repos, | ||
|
@@ -43,7 +43,7 @@ beforeEach(() => { | |
}); | ||
|
||
afterEach(() => { | ||
actions.kube = { ...kubeaActions }; | ||
actions.kube = { ...kubeActions }; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the cleanup. |
||
spyOnUseDispatch.mockRestore(); | ||
}); | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's see who gets there first (you and Rafa are both updating in your PRs :) ).