Matthias Dellweg
Matthias Dellweg
> as long as we're not removing any fields that come from metadata/manifest, this should be fine. > > We definitely need to keep fields such as `metadata["repository']`. That metadata...
Where does the name `v3/plugin/ansible/namespaces/` come from? I'm fine with whatever you want the v3 api to be structured. Just curious what kind of a plugin you are referring to...
Docs and how we build / test them have changed completely. I cannot envision this issue is still valid.
That comment may be wrong. If I remember correctly, the static file are copied to the nginx (pulp-web) container and served from there. Edit: But maybe that's not true anymore?...
I'm unsure what the naively expected condition should be. We could also add "1" or check for "set and not empty".
I'm certain, both versions are allowed per the docker compose docs (or at least were). But the change you made sounds fine. We could use a PR then.
It's absolutely worth a PR. Also we don't release the compose files from this repository.
This nightly tagged container image is built nightly from all the main branches. This will never be considered stable. This nightly build from GA'd released plugins is called 'latest'.
As long as we think we might eventualy ga those plugins, i see no conflict here. It's something that may eventually become the official pulp single container. Also this CI...
The only thing to hold you back is that this might be an unwarranted request to bump the pulpcore dependency.