You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2024. It is now read-only.
Support two repository types: sync and modify. Sync repositories pull content in from an external AH instance (e.g., Community Hub, AH Cloud, another private AH) and are read only. Modify repositories can be used for CLI publish, install and promote operations. API: Add support for repository management #210
Expose repositories via URL path. For example, to publish a collection to repository-a, a user would publish to /api/v3/repository-a/artifacts/collections. API: Add support for repository management #210
Continue to support the single repository model in AH Cloud (i.e., leave AH Cloud the way it is)
When content comes into a modify type repository (either through publish or promotion), automatically create a new namespace, if it does not already exist. Namespaces will be unique within a repository. Example: When user promotes geerlingguy.foo from the Community sync repo to a modify repo, the geerlingguy namespace is automatically created. API: Automatic namespace creation within a repository #216
repository-a
, a user would publish to/api/v3/repository-a/artifacts/collections
. API: Add support for repository management #210collection promote
command to the CLI that copies content from one repository to another. CLI: collection promote command #212, API: Add endpoints to support content promotion #217geerlingguy.foo
from the Community sync repo to a modify repo, thegeerlingguy
namespace is automatically created. API: Automatic namespace creation within a repository #216The text was updated successfully, but these errors were encountered: