-
Notifications
You must be signed in to change notification settings - Fork 144
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
feat: support of export single project/workflow/job #836
Conversation
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.
I'm adding comments for job templates that also apply to the other modified objects
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.
LGTM
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.
Please, fix the errors listed by the linter
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.
LGTM
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.
LGTM
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.
LGTM, but a changelog fragment file needs to be created: changelogs/fragments. Something similar to:
Minor Changes:
- filetree_create able to filter by project_id, workflow_job_template_id or job_template_id
https://github.com/redhat-cop/controller_configuration/blob/devel/changelogs/config.yaml
Ok, I've added the missing changelog, anything more to add? |
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.
LGTM
* feat: support of export single project/workflow/job * fix: missing project_id parameter * lint: fix indention * fix: query param wrongly defined * misc: fix issue witch checks, rename variables, remove unneeded conditions * rew: modify conditionals for project/job_template/workflow * fix: missing commas * fix: missing comma and aligment * fix: remove trailing whtiespaces * fix: remove project_id from query of workflow * fix: wrong parameter in query * rev: undo project_name support added by mistake * fix: add missing changelog entry --------- Co-authored-by: Przemyslaw Kalitowski <[email protected]>
* feat: support of export single project/workflow/job * fix: missing project_id parameter * lint: fix indention * fix: query param wrongly defined * misc: fix issue witch checks, rename variables, remove unneeded conditions * rew: modify conditionals for project/job_template/workflow * fix: missing commas * fix: missing comma and aligment * fix: remove trailing whtiespaces * fix: remove project_id from query of workflow * fix: wrong parameter in query * rev: undo project_name support added by mistake * fix: add missing changelog entry --------- Co-authored-by: Przemyslaw Kalitowski <[email protected]>
What does this PR do?
The tasks should allow users to easily export all objects related to a specific project.
Currently, filetree_create retrieves every project and other defined objects, which is not desirable in the following use case scenario.
Use case scenario example for a project:
How should this be tested?
Manual
Is there a relevant Issue open for this?
N/A
Other Relevant info, PRs, etc
Request on the forum, that what we want to achieve: https://forum.ansible.com/t/rfe-develop-new-functionality-for-exporting-configurations-filtered-by-project/5220