-
Notifications
You must be signed in to change notification settings - Fork 76
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
fix: Hide fleet selection from settings #13848
Conversation
Jenkins BuildsClick to see older builds (12)
|
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.
Removing is ok, not sure only about the point @richard-ramos made in this comment.
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.
The implementation (de-implementation I'd say 😄) is good with me.
Explaining the mark as 'request changes' below.
Indeed there was a discussion today to keep this selector, but make it "more dev-usage-only obvious". E.g. move to some "Debug section", or only allow to change when Debug
is enabled, smth like that. Or even keep it as is, but add some exaplnating label.
The reason why to keep this is to be able to test deployed fleets with Status apps. Recently we faced an issue because shards.test
fleet was upgraded. This wouln't happen if the upgrade was first done on .test
fleet, tested by Status QA team and then deployed to .prod
fleet.
This workflow also requires switching status to prod
.
OK then the most straightforward solution would be to just hide it in |
- hide the Fleet settings in production builds; will be visible in dev or testing builds Fixes #13848
5e1009c
to
e4d9e5f
Compare
Yes, until we want to test this with prod release 😄 Let's see what other people response. I'll tag @jrainville as well for context. |
If we want QAs to test, then hiding it in production is not the best, because QAs mostly use CI builds that are in production. Doing something like Igor said is probably the simplest. Hide it when not in Debug, or we can add a new switch in the Advanced section to hide it. |
It is already in the Advanced section; I'll add an envvar so that we can enable it at will (by default this will be hidden) |
- introduce `ENABLE_FLEET_SELECTION` envvar to control the Fleet selection UI availability - hide the Fleet settings by default, unless `ENABLE_FLEET_SELECTION=1` Fixes #13848
e4d9e5f
to
6881e3f
Compare
Ok, third time's a charm :) @jrainville @igor-sirotin @anastasiyaig |
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.
Maybe go with some more generic solution with desktop config?
status-desktop/src/env_cli_vars.nim
Line 92 in 96d9acf
type StatusDesktopConfig = object |
- introduce `ENABLE_FLEET_SELECTION` desktop config entry to control the Fleet selection UI availability - UI can be enabled with envvar `STATUS_RUNTIME_ENABLE_FLEET_SELECTION=1` Fixes #13848
6881e3f
to
7e17796
Compare
@igor-sirotin ok, updated with the suggestion; I hope it's fine now 😆 |
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.
Looks good to me! Thank you!
What does the PR do
ENABLE_FLEET_SELECTION
desktop config entry to control the Fleet selection UI availabilitySTATUS_RUNTIME_ENABLE_FLEET_SELECTION=1
Fixes #13848
Affected areas
Settings/Advanced
Screenshot of functionality (including design for comparison)
Disabled by default:
With
ENABLE_FLEET_SELECTION=1
: