- Email: firstname.lastname@example.org
- Registered on: 12/17/2014
- Last connection: 09/30/2019
- Pulp (Developer, 12/17/2014)
- RPM Support (Developer, 12/17/2014)
- Puppet Support (Developer, 12/17/2014)
- Docker Support (Developer, 12/17/2014)
- Python Support (Developer, 12/17/2014)
- Packaging (Developer, 12/17/2014)
- Crane (Developer, 12/17/2014)
- OSTree Support (Developer, 12/17/2014)
- Debian Support (Developer, 12/17/2014)
- Nectar (Developer, 12/17/2014)
- External (Developer, 03/21/2017)
- File Support (Developer, 07/17/2017)
- Ansible Plugin (Developer, 08/20/2018)
- Maven Plugin (Developer, 09/18/2019)
- Pulp CLI (Manager, 07/09/2018)
- Container Support (Developer, 12/06/2019)
Write script based workflow docs for content mgmt Revision 8ddb1c12: Merge pull request #413 from asmacdo/mgmt-script-docs
Also, execute these scripts as part of the docs test job on travis.
[noissue] Revision 4df4897b: Write script based workflow docs for content mgmt
Add url prefix to plugin urls Revision 59d93c8b: Merge pull request #415 from asmacdo/restrict-urls
This seems fixes the issue (forcing the use of /pulp/api/v3/) for pulp_docker. https://github.com/pulp/pulp_docker/pull/415/ Issue #5486: Plugin url patterns allow an arbitrary base path (not just /pulp/api/v3/)Original:
In each of their generated docs I noticed the endpoints all looked like ...
Task #2946 (NEW): As a plugin writer, I know how to publish docs to RTDHere are some points to take into account:
* we want plugin docs to be built independently from the core ones
* not to be blocked from building docs due to error in plugin docs (this is especially relevant to the community plugi...
Story #4637 (NEW): As a plugin writer, I know how to publish REST API docshttps://pulp.plan.io/issues/4636 is how pulpcore will publish REST API docs. This strategy will work best if plugins do this as well, because many of the user-facing REST calls are plugin-specific.
This story is to share the process f...
Applied in changeset commit:pulp_docker|fbc9074078bf4c324c3820bd3201449410ba95ad. Issue #4549: Removing docker manifests from a docker repository takes a long timeRemoving all docker manifests from a large docker repo seems to take a long time:
~300 manifests takes ~2 minutes
~2000 manifests takes ~30-40 minutes
1. Create and sync a docker repo such as: https://quay.io ...
Applied in changeset commit:pulp_docker|fbc9074078bf4c324c3820bd3201449410ba95ad. Issue #5161: Removing manifest_lists from a repository does not purge all newly unlinked manifestsTo reproduce:
1. Sync busybox
2. Create a new repo foo
3. add all manifest_lists from busybox to foo
4. remove all manifest lists from foo
5. check content unit counts, some manifests (and their referenced blobs) are still in foo
Also available in: Atom