-
Epic
-
Resolution: Done
-
Major
-
None
-
crc-2023-06-27
-
None
-
CRC logos all Ansible
-
False
-
-
False
-
Not Selected
-
In Progress
-
0% To Do, 0% In Progress, 100% Done
-
-
-
Team Discussion
Collection lists now use the ansible A logo, instead of the logo associated with their namespace.
(This is because we switched to the collection version search API, and the logo information is not available anymore. (namespace_metadata is null, logo needs namespace_metadata.avatar_url)
(found when checking crc-2023-06-27, but possibly also present in standalone)
May not be a bug, may be intentional.
There are likely 3 issues occurring
- The galaxy namespaces haven’t been converted into pulp namespaces
- This means the collection version endpoint `namespace_metadata` will be null. This is solved by edited and saving a namespace or running download-namespace-logos.py
- Index rebuild has not run
-
- This means that if there is a pulp namespace, only newly added collection versions will get the `namespace_metadata` populated. This may get solved by running download-namespace-logos.py which may trigger an index rebuild (after the namespace models edits, and the add_remove call will trigger a repo v bump, which will by proxy trigger an index rebuild)
- When the `namespace_metadata` is populated, the `avatar_url` is null
- This content app issue may be resolved with
AAH-2213and then removing the workaround in galaxy_ng
- This content app issue may be resolved with