Bug 2170858

Summary: [RFE] Support for external capsule\smart-proxy sync via Satellite\Foreman Ansible Collection
Product: Red Hat Satellite Reporter: Amit Agarwal <amiagarw>
Component: Ansible CollectionAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: bgajjava, dsinglet, ehelms, jalviso, jangerrit.kootstra, saydas
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amit Agarwal 2023-02-17 12:58:50 UTC 
1. Proposed title of this feature request.

   Support for external capsule\smart-proxy sync via Satellite\Foreman Ansible Collection 

2. What are the nature and description of the request?

   The end-user needs to perform capsule sync using an ansible playbook instead of manual sync and even though we can create a playbook with command\URI module + hammer\API, It would be great to have an support ansible module within the satellite ansible collection that reduces the manual effort.  

3. Why do you need this? (List the business requirements here).

   Content Views publication or promotion creates a set of Capsule syncs so the end wants to stop automated sync and create one single capsule sync task  at the end of all publications/promotions and perform capsule sync using Ansible play instead of manual sync


4. How would you like to achieve this?

  We expect to have a different module created for smart_proxy_sync and supported through https://console.redhat.com/ansible/automation-hub/redhat/satellite/docs

5. Expected results:

The developed module should be able to mimic any behavior that the "hammer capsule content synchronize" can i.e. we should be able to sync an LCE, CV or even a Repo [ when the ID\name is properly used ]

6. Would you be able to assist in testing this functionality if implemented?
   Yes
Comment 2 ir. Jan Gerrit Kootstra 2023-02-23 18:35:28 UTC 
To add to point 6.

We have facilities to do alpha/beta testing and pre-prod testing.