-
Notifications
You must be signed in to change notification settings - Fork 359
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
data: profile: extend workstation profile to hide pages for Web UI #6047
Conversation
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.
You also need to extend anaconda.conf with the defaults of the field. Also please add comments.
I also wonder if it shouldn't be hidden_webui_pages
to be crystal clear.
I am in for the clarification. |
I am in for the clarified version. |
1c56415
to
3d7771b
Compare
3d7771b
to
9683d73
Compare
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. :)
Longer term we might need something more granular and/or dynamic, but this should work fine for now. :)
/kickstart-tests --waive webui config |
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.
So I was re-thinking about this. I dont think screen is the correct item to specify hiding. I think we should allow hiding components .
The issue is that the screens might incorportate multiple configurations, aka language together with keyboard and timezone.
Maybe we want to keep the language selection for Workstation, but we dont want the timezone.
I believe we need some more fine grained approach here.
What do you think? @jkonecny12 @M4rtinK
Sounds like a good approach. We just need to make it easy to list possible options. It could be comments in the configuration file? |
Sorry now that I am rethinking this, this would complicate things quite a lot code wise. So I suggest to ignore my comment, start by disabling wizard page level components, and and if in the future the design forces us to be more specific, I will re-think it. |
Previously we would be using the ISO variant (Boos, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
9683d73
to
a39a497
Compare
a39a497
to
a48496d
Compare
Previously we would be using the ISO variant (Boos, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
Yeah - while it would be ideal to work on the level of features, that also implies being able to map the features to pages & the resolve if the given page has all features it provides hidden. Far from simple I'm afraid + added complication due to inter page dependencies. (eq. storage page should go before software selection page, so it can check there ie enough space). Working on page level is much more blunt bot certainly far simpler for now. :) |
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
a48496d
to
e756cfd
Compare
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
@@ -22,6 +22,9 @@ hidden_spokes = | |||
NetworkSpoke | |||
PasswordSpoke | |||
UserSpoke | |||
hidden_webui_pages = | |||
anaconda-screen-accounts |
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.
Do we need the prefix? Will it be a situation when it is not anaconda-screen
prefix?
If yes, could you please document it somewhere (commit message for example)?
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.
This has been discussed more in the web UI PR rhinstaller/anaconda-webui#551 (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.
I see, ok.
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.
I would still like to see the reasoning as part of the commit if possible.
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. Thanks!
Previously we would be using the ISO variant (Boot, Live) from Anaconda configuration file and we would conditionalize the page visibility in the Web UI code according to that. With this commit, the pages can be hidden per-new option of the configuration file [1]. [1] rhinstaller/anaconda#6047
This was previously handled within the Web UI codebase. Now we hide pages specified by the `hidden_webui_pages` configuration option. The hidden_webui_pages configuration option accepts an array of strings mapping to Web UI wizard screen selectors. The are using the 'anaconda-screen-' prefix followed up by the screen purpose. So 'anaconda-screen-accounts', 'anaconda-screen-language'. Using the prefixes would make it easier to find all places where it is used (tests, codebase etc) & possibly make it less likely to be broken by mistake.
e756cfd
to
9b54f34
Compare
/kickstart-tests --waive web ui only |
This was previously handled within the Web UI codebase. Now we hide pages specified by the
hidden_pages
configuration option.Related to: rhinstaller/anaconda-webui#551
Related to: https://issues.redhat.com/browse/INSTALLER-4085