temporary API endpoint for custom virtual env data #10007
Closed
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 succeeded.
|
|
closing this in favor of new work that will shift this logic into an awx-manage command, see #7062 for full history |
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.
SUMMARY
related to: #7062
This creates a new API endpoint for custom virtual environments. It spits out the pip freeze data for the custom virtual environments so that data can be used to create an execution environment with the same requirements, should that be desired.
This API endpoint will not be long lived and will only be used to help with the transition from Custom Venvs to Execution Environments.
ISSUE TYPE
COMPONENT NAME
AWX VERSION