-
Feature Request
-
Resolution: Done
-
Undefined
-
None
-
2.4
-
False
-
-
False
What is the nature and description of the request?
Currently AAP git project synchronization is performed from one controller.
If sync fails on one controller, why to sync again on all of them? Especially if controller is behind unstable proxy on slow network (cruise ship) for example.
Why does the customer need this?
If sync fails on one controller, due to temporary network problems, we need a way how to sync projects on just failed nodes.
How would you like to achieve this?
Api parameter to select node, where to copy and sync the project
Webui option to select nodes for sync if needed
List any affected known dependencies:
Controller API, Controller Web UI, Project updates playbooks.
- is duplicated by
-
AAPRFE-1264 Add an option to force Git project synchronization on all controllers at once.
-
- Backlog
-