Goal:

Edge API orchestrates the creation and use of a new ostree repo in Pulp.

• Edge API needs to request Pulp create a new ostree repo
• Edge API needs to request Pulp configure security for the new ostree repo
• Edge API needs to request Pulp create a Distribution to make the ostree repo accessible
• Edge API needs to use the Pulp repo to request an ISO if selected in the UI--typical of version 1 of an image(set)

Acceptance Criteria:

• Pulp creates a new repo based on a request from Edge API
• Pulp creates a Distribution for the repo based on a request from Edge API
• The repo is accessible by Image Builder to push new commit updates
• The repo is accessible by Edge API to read ostree data
• The repo is accessible ONLY by system(s) registered with the same orgid that created the commit via Image Builder
• Edge API can request an installer ISO from Image Builder using the new repo for content (per the existing Edge API process with AWS)

NOTE: Access to manage the repo outside of the consoledot applications (e.g., on-prem) is not in scope for this Feature/Epic.

Open questions:

• What is the effort to backport write access to existing repos if needed in the future?
  Does it make sense to give Edge API write access to repos now?