Skip to content
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

Fixes #37959 - Allow optimized:false sync for ansible collections #11284

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

sjha4
Copy link
Member

@sjha4 sjha4 commented Jan 22, 2025

What are the changes introduced in this pull request?

Ensure Full smart proxy Sync triggers non-optimised pulp sync for ansible collections.

Considerations taken when implementing this change?

See: #11168 for more context
Checked the ansible sync API here: https://pulpproject.org/pulp_ansible/restapi/#tag/Repositories:-Ansible/operation/repositories_ansible_ansible_sync
The optimize flag is supported here like yum, apt repos.

What are the testing steps for this pull request?

  1. Create a collection repo
  2. Sync it to a smart proxy
  3. Run a complete sync on capsule.
  4. Make sure pulp receives optimized:false on the proxy.

@sjha4 sjha4 force-pushed the collection_optimized_sync branch from b06f12e to 8b549ce Compare January 23, 2025 16:14
Copy link
Contributor

@qcjames53 qcjames53 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Samir! I was able to verify the changes to the pulp remote request occur during full smart proxy sync with ansible collections. The remote request remains the same for other content type/sync type combinations. The testing changes seem reasonable and I believe no further test coverage is necessary. ACKing!

@sjha4 sjha4 merged commit 62f5a5c into Katello:master Feb 4, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants