# Deprecation status sync

Issue: https://pulp.plan.io/issues/7834

we have 2 options:
- Create a new repository version for deprecation status changes
- Modify the deprecation status of the latest repo version

## Create a new repository version for deprecation status changes

#### Don't use the RepositoryVersion context manager

1. Have AnsibleDeclarativePipeline define a `def create()` method. Have it not use the context manager

repo.latest_version().content

## Modify the deprecation status of the latest repo version

#### Idea

1. Add a stage that collects the deprecated values for all collections in memory. Maintain a reference to that deprecated info when AnsibleDeclaratibePipeline is created here https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/collections.py#L81
2. Wait for control to be returned to the sync code here https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/collections.py#L82. Apply the deprecated status info from (1) to the new (or old) repository version

---
Pulp to Pulp sync tests
- only deprecation status change
- one new collection + older collection with new deprection status