add LegacyRoleImport model to store galaxy-importer logs for legacy imports #1829
+53
−1
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
…mports No-Issue Signed-off-by: eamontracey <[email protected]>
github-actions
bot
added
backport-4.2
EamonTracey
removed
backport-4.2
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.
When a legacy role is imported, galaxy-importer calls ansible-lint on the role. Currently, those logs remain unused by galaxy_ng, but ideally, they will be accessible and shown to users when they import a legacy role.
This PR largely mirrors how collection import logs are handled by pulp_ansible. A new
LegacyRoleImportmodel is created for each legacy role import task. ALegacyRoleImportHandlerwhich inherits fromlogging.Handlerwill emit all log records into the correspondingLegacyRoleImportmodel.