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

Make ui_next the default UI #15347

Closed
wants to merge 15 commits into from
Closed

Make ui_next the default UI #15347

wants to merge 15 commits into from

Conversation

fosterseth
Copy link
Member

@fosterseth fosterseth commented Jul 9, 2024

How to test

make target changes

New:
ui-legacy
ui-legacy-release
clean-ui-legacy

Changes (run these OUTSIDE awx containers, requires nodejs >= 18)
ui-devel - this now makes new UI
clean-ui - cleans new UI files

SUMMARY

Make the newer UI next the default UI experience.

Serves up old UI at /ui_legacy

pairs with ansible/awx-operator#1923

image

ISSUE TYPE
  • New or Enhanced Feature
COMPONENT NAME
  • API
TODO
  • remove welcome popup from ansible-ui
  • remove "tech preview" language from banner
  • make banner point to /ui_legacy/ instead of /

@fosterseth fosterseth changed the title Make ui_next default Make ui_next the default UI Jul 9, 2024
@samccann
Copy link
Contributor

Just a general comment - having links with 'here' as the text don't work well with screen-readers. It is better to have something more descriptive in that bit of text.

awx/main/views.py Outdated Show resolved Hide resolved
@AlanCoding
Copy link
Member

Screenshot from 2024-07-19 14-49-20

When I go to the dev environment I get this. What do I need to run the dev environment with the new UI?

@AlanCoding
Copy link
Member

In the container I get:

bash-5.1$ make ui-next
make: Nothing to be done for 'ui-next'.

awx/settings/defaults.py Show resolved Hide resolved
@@ -79,8 +77,8 @@ function Dashboard() {
<Banner variant="info">
<Trans>
<p>
<InfoCircleIcon /> A tech preview of the new {brandName} user
interface can be found <a href="/ui_next">here</a>.
<InfoCircleIcon /> The new user interface can be found{' '}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't use "here"
Maybe you the link should be "enable new user interface"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reworded it, see photo in opening body

awx/ui/src/screens/SubscriptionUsage/SubscriptionUsage.js Outdated Show resolved Hide resolved
@gundalow
Copy link
Contributor

Screenshot from 2024-07-19 14-49-20

When I go to the dev environment I get this. What do I need to run the dev environment with the new UI?

Do we need a check in the makefile to validate the UI is available, ie fail early.

@AlanCoding
Copy link
Member

@gundalow I just want to know how to use this the first place. I read awx/ui_next/README.md (from hints in root Makefile) and set UI_NEXT_GIT_REPO to the git address for https://github.com/ansible/ansible-ui and the target still gives the same result.

@fosterseth
Copy link
Member Author

fosterseth commented Jul 19, 2024

to use

  1. from awx repo run make ui-next (outside the container)
  2. make docker-compose

Do we need a check in the makefile to validate the UI is available, ie fail early.
@gundalow

this isn't too different than how it was before, where users had to manually run make ui-devel after starting containers

@gundalow
Copy link
Contributor

this isn't too different than how it was before, where users had to manually run make ui-devel after starting containers

Does this need to go into the contributing/devel docs somewhere?

Make the newer UI next the default UI
experience.

Enable legacy ui

https://<controller_url>/ui_legacy

will redirect to the old user interface

Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
@fosterseth
Copy link
Member Author

Does this need to go into the contributing/devel docs somewhere?
@gundalow

I added some documentation on installing the legacy UI

@djyasin djyasin self-requested a review July 24, 2024 13:25
Copy link
Member

@djyasin djyasin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was able to pull down these changes and walk through the steps provided to successfully build ui_next and then the legacy UI with no issues.

TheRealHaoLiu and others added 5 commits July 24, 2024 14:59
instead of building the ui during make sdist build the ui ahead of time in different docker build stage
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Copy link

sonarcloud bot commented Jul 25, 2024

@fosterseth
Copy link
Member Author

no longer plan to serve old UI alongside new UI

closing in favor of #15405

@fosterseth fosterseth closed this Jul 26, 2024
@fosterseth fosterseth deleted the ui_next_default branch August 1, 2024 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants