dkliban@redhat.com
dkliban@redhat.com- Registered on: 12/17/2014
- Last connection: 08/10/2020
Issues
- Assigned issues: 3
- Reported issues: 450
Projects
- 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, 02/10/2015)
- Crane (Developer, 02/10/2015)
- OSTree Support (Developer, 02/10/2015)
- Debian Support (Developer, 02/10/2015)
- Nectar (Developer, 02/10/2015)
- File Support (Developer, 07/17/2017)
- Infrastructure (Developer, 11/29/2017)
- Ansible Plugin (Developer, 08/20/2018)
- Maven Plugin (Manager, Developer, 04/21/2018)
- Pulp CLI (Manager, Developer, 07/09/2018)
- CertGuard (Developer, 04/06/2020)
- Container Support (Developer, 12/06/2019)
- NPM Plugin (Developer, 05/11/2020)
- Migration Plugin (Developer, 01/14/2020)
Activity
08/10/2020
-
Task #7285 (ASSIGNED): Add documentation about distributing the Certificate CA generated by Pulp InstallerThe user needs to be provided with information about 3 scenarios:
Pulp Installer generated a CA certificate, created an SSL certificate that is signed by that CA, and configured .
Pulp Installer user provided an SSL certificate and...
08/07/2020
-
Import or generate key for token authentication Revision af31b1d2 (ansible-pulp3): Merge pull request #361 from mdellweg/install_token_keys
-
Import or generate key for token authentication Revision af31b1d2 (ansible-pulp): Merge pull request #361 from mdellweg/install_token_keys
-
Yes, this is for 3.6. I am about to start working on this. Task #7285: Add documentation about distributing the Certificate CA generated by Pulp InstallerThe user needs to be provided with information about 3 scenarios:
Pulp Installer generated a CA certificate, created an SSL certificate that is signed by that CA, and configured .
Pulp Installer user provided an SSL certificate and...
08/05/2020
-
Task #7285 (POST): Add documentation about distributing the Certificate CA generated by Pulp InstallerThe user needs to be provided with information about 3 scenarios:
Pulp Installer generated a CA certificate, created an SSL certificate that is signed by that CA, and configured .
Pulp Installer user provided an SSL certificate and... -
It looks like you were trying to install pulp_python which didn't have a 3.5.0 compatible release yet. We are about to publish it to PyPI now. Issue #7223: pulpcore/plugin compatibility check failure in pulp_common using pulp_installer 3.4.1 and 3.5.0 on fresh centos 8.2.2004 vmAs described in [this pulp-list thread[https://www.redhat.com/archives/pulp-list/2020-July/msg00012.html]], I'm trying to bring up a basic pulp instance, using a standard, freshly installed centos 8.2.2004 vm, and my pulp.yml does not ge...
-
Forbid the methods PATCH and PUT for push repositories Revision 1cc92318 (pulp_container): Merge pull request #127 from lubosmj/forbid-push-repo-update-7013
-
-
Yes, we should only allow users to delete Push repositories via Pulp's REST API. If the delete occurs while a user is pushing to this repository, at some point the user will start getting a 404 response from the registry API. Task #7172: Delete a distribution along with a push repository
When a push repository is going to be deleted, a distribution that references this repository needs to be deleted as well.
**Question remains:**
Should we DELETE a push repository via the pulp api? We should enable users to remove ... -
Also available in: Atom
.