remove custom_virtualenv support from the AWX collection and docs #9498
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build failed.
|
ryanpetrello
force-pushed
the
bye-bye-virtualenv
branch
from
0f79e95 to
db62ac7
Compare
|
Build failed.
|
ryanpetrello
force-pushed
the
bye-bye-virtualenv
branch
from
db62ac7 to
b2a4340
Compare
|
Build failed.
|
ryanpetrello
force-pushed
the
bye-bye-virtualenv
branch
from
b2a4340 to
4c60999
Compare
|
Build succeeded.
|
|
Build succeeded (gate pipeline).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
cc @rebeccahhh @shanemcd @jbradberry
Until we address tooling for identification/migration of these (later: #7062), I thought it might make sense to remove this from our docs and collection to discourage people from using these (since the API still technically allows you to set the field).