Ansible Plugin

https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/models.py#L237-L265

https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/repository.py#L786-L820

If the deprecation was the only thing that changed from the last version, the new version will be deleted, therefore the deprecation status won't get updated

Test scenario:

• sync

• modify deprecation status from one collection

• sync again

• verify the deprecation corresponds with the remote source

• verify a new repository version was created

Question: should deprecation status be synced only on mirror mode?

The syncing in these examples: from where? Since we can only "set" deprecated on the local pulp system it would need to be a pulp-to-pulp sync, but I suspect these are from actual remote sources like galaxy.

I expected sync to occur on all sync types, mirror and otherwise.

I think the current bug comes in because since Pulp has already saved the content locally and the changing of deprecated state info occurs at save time it ends up not updated the changed deprecated state for content it already saved into that repo. Basically it's a re-sync bug due to the setting of deprecated data being set only on newly saved units here.

the tests scenario I thought was not valid, since the deprecation is being changed locally, and for the reported issue it happens at server side

https://hackmd.io/@pulp/issue7834

PR: https://github.com/pulp/pulp_ansible/pull/431