Bug 2170858 - [RFE] Support for external capsule\smart-proxy sync via Satellite\Foreman Ansible Collection
Summary: [RFE] Support for external capsule\smart-proxy sync via Satellite\Foreman Ans...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.12.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-17 12:58 UTC by Amit Agarwal
Modified: 2023-08-12 23:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16360 0 None None None 2023-03-08 13:27:17 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.