Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

The feature will allow pinning of a version of a catalog to a digest and will keep the history of what was mirrored.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

<your text here>

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

From this spike: CLID-410
Currently one of the solutions in oc-mirror to keep the state of an operator catalog unchanged is to pin the catalog by digest. 

This process currently is manual and it could be automated by saving a file after processing the latest operator catalog. This file could have date and time as its file name and its content would have the operator catalog digest and all operator and related images digests on that specific run. 

This file could be read by customers by some kind of terminal viewer so they can decide which file to use when multiple files are stored. This file could follow the ImageSetConfiguration structure or could be a different one. 

There are three sub-tasks on this spike:

• Convert automatically the tag to a digest, but in a way that is possible to know for each operator catalog version this digest belongs to (it could be some kind of annotation in the ImageSetConfiguration or in another way.
• Save in a file or a commit (in an immutable way - checksum or git) what catalog digest and version was mirrored, what operator versions were mirrored, what was the workflow (m2m, m2d, or d2m), date and time.
• The customer needs to be able to view the history of what was mirrored with all the stored data. This could work together with the current history to do the tar diff.

  Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>