Use update:ui rake task, instead of update:bower #15578
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea being that the UI should know what to update, not the backend..
Right now, as of ManageIQ/manageiq-ui-classic#1699,
update:ui
just runsupdate:bower
andupdate:yarn
.It will soon also run
webpack:compile
, and eventually dropupdate:bower
, none of which should visible on the backend.This just updates all the mentions of
update:bower
withupdate:ui
in manageiq/.Similar PRs to appliance-build and manageiq-pods will follow.