Why it’s important:
Namespaces are utilized by both community galaxy (for authors), and Hub (for partners). Being able to scope all content available by these groups is necessary in order to support finding and identifying content.
Namespace information includes key identifiers for our partners, such as logos, contract information, documentation and links to other resources that they want to share with users. It is required that this information be able to sync down to PAH, through HTTPS-based sync, as well as through import/export to air gapped environments
Global namespace syncing doc: https://docs.google.com/document/d/1cciDPJSFASeUFgGFOpPwDWJOZS2caqmf8fobwnOcA68/edit#heading=h.l56o7l468jcd
Estimate notes:
~ 2 weeks for engineering, mostly UI lift
TBD on QE
- blocks
-
AAH-2468 Hub > Namespaces
- In Progress
-
AAH-2346 namespace metadata queries are eating database CPU
- Closed
- is blocked by
-
AAH-1398 API Refactor - moving remainder of v3 API models and endpoints to pulp ansible
- Backlog
-
AAH-2358 Upgrade to latest Django LTS (4.2.1)
- Closed
-
AAH-2293 Namespace search APIs
- Code Review
-
AAH-759 Add missing galaxy ng namespace endpoints to pulp ansible
- Release Pending
- is depended on by
-
AAH-1776 Collection Repository Management - P1 use cases [blocker]
- Closed
- is duplicated by
-
AAH-314 Namespace and Logo Sync
- Closed
- is related to
-
AAH-2034 Namespace & Logo sync planning
- Closed
- links to