jchristi
- Login: jchristi
- Registered on: 10/17/2016
- Last connection: 01/23/2018
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 1 | 1 |
Projects
Project | Roles | Registered on |
---|---|---|
Container Support | Private Access | 12/06/2019 |
Crane | Private Access | 10/17/2016 |
Debian Support | Private Access | 10/17/2016 |
Docker Support | Private Access | 10/17/2016 |
File Support | Private Access | 07/17/2017 |
Migration Plugin | Private Access | 01/14/2020 |
Nectar | Private Access | 10/17/2016 |
OSTree Support | Private Access | 10/17/2016 |
Packaging | Private Access | 10/17/2016 |
Pulp | Private Access | 10/17/2016 |
Puppet Support | Private Access | 10/17/2016 |
Python Support | Private Access | 10/17/2016 |
RPM Support | Private Access | 10/17/2016 |
Activity
11/30/2017
-
@bmbouter sure, I can collaborate on this. As for my use case, I really don't need the git storage backend as long as there is support for forwarding to a private gitlab instance (which I believe the latest galaxy source code can).
Story #2345: Feature Request: Add support for private Ansible Galaxy in Pulp**User Story**
As a pulp user, I would like to be able to host a private instance of Ansible Galaxy with Pulp so that my organization can share and reuse Ansible roles across teams without having to use the public galaxy.ansible.com (...
10/18/2016
-
Story #2345 (CLOSED - CURRENTRELEASE): Feature Request: Add support for private Ansible Galaxy in Pulp**User Story**
As a pulp user, I would like to be able to host a private instance of Ansible Galaxy with Pulp so that my organization can share and reuse Ansible roles across teams without having to use the public galaxy.ansible.com (...
Also available in: Atom