-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Remove custom virtual env #9570
Remove custom virtual env #9570
Conversation
@tiagodread @unlikelyzero this still a working in progress, but I will run the e2e tests. I believe this one will disrupt a lot tests. |
250eb3e
to
99c7beb
Compare
Build succeeded.
|
Adding more unit-tests. |
Build succeeded.
|
<span> | ||
<Tooltip | ||
content={i18n._( | ||
t`Custom virtual environment ${virtualEnvironment} must be replaced by an execution environment.` |
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.
cc @shanemcd @wenottingham @tvo318 we may want to come up with some instructions (at some URL) for doing so - I have to imagine we'll have some type of knowledge base article or documentation that describes the transition process - do we want to file an issue to track this work so we don't forget it later?
I updated the settings. Good find @one-t. If you want to take another look. |
Build succeeded.
|
Hey @one-t, we do show warnings about missing EE on lists for - Orgs, Projects, Inventory Sources, and Job Templates. We also show warnings on details pages for those resources. As we talked, based on your feedback I will make the message on the list to have the custom virtual env to be replaced as shown on the details page. That is a good suggestion. |
Remove custom virtual from the UI. Also, surface missing-resource warnings on list items for UJTs that were using custom virtualenvs. Fix some uni-tests warnings. See: ansible#9190 Also: ansible#9207
@one-t, updated. Now the same message is displayed on the lists and details. I triggered the e2e tests again to verify the latest changes. |
Build succeeded.
|
Build succeeded (gate pipeline).
|
Remove custom virtual from the UI.
Also, surface missing-resource warnings on list items for UJTs that were using
custom virtualenvs. And related details page.
See: #9190
Also: #9207