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

Updates to UI Remote build feature #10721

Open
richard-cox opened this issue Mar 28, 2024 · 0 comments
Open

Updates to UI Remote build feature #10721

richard-cox opened this issue Mar 28, 2024 · 0 comments
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

  • Default ui-offline-preferred to Local (note the actual value might not be that string)
    • Change in rancher/rancher repo
  • Remove the defaults for ui-index and ui-dashboard-index
    • Change in rancher/rancher repo
    • Update references in our docs to contain the values that were removed
    • Add info to our docs on how to supply them, and change ui-offline-preffered, as helm and docker cli args
    • Announce change to extended team
  • Add a disclaimer shown when setting ui-index or ui-dashboard-index
    • Above input, only when editing or modal?
    • TBD but something like 'Use of Rancher Artifacts requires acceptance of the SUSE EULA'

The above changes, in particular how it affects -head builds, should be announced to the wider team. This should contain instructions on how to install rancher with the previous env (for example if QA need to test setup process changes)

@richard-cox richard-cox added this to the v2.10.0 milestone Mar 28, 2024
@nwmac nwmac added [zube]: To Triage QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Mar 28, 2024
@nwmac nwmac modified the milestones: v2.10.0, v2.11.0 Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

3 participants