Re: [Pulp-dev] Read access in Github

2020-02-21 Thread Fabricio Aguiar
Travis mentions something about 24h sync: https://docs.travis-ci.com/user/travis-ci-for-private/#who-has-access-to-the-builds For me, I had to go to my profile on travis, click in sync account, after that, I was able to restart travis jobs Best regards, Fabricio Aguiar Software Engineer, Pulp Pro

Re: [Pulp-dev] Read access in Github

2020-02-21 Thread David Davis
Unfortunately, the Github interface doesn't allow people/repos to be added to a team in bulk. I have to add them one by one. So I added most of the main repos I could think of that are still active and most of the people that aren't Pulp org admins to a new team called Contributors. If I missed any

Re: [Pulp-dev] Importers/Exporters

2020-02-21 Thread David Davis
I also want to make it easy for the user. I don't think we should support repositories now though. We're strapped for time, Katello doesn't need it at the moment, and I think we can add it later. Another argument for breaking up parameters is that we need to support incremental exports. I think th

Re: [Pulp-dev] Importers/Exporters

2020-02-21 Thread Dennis Kliban
We can't provide any data from the Katello database, but we can provide enough data for the archive to contain all the published metadata and distributions needed to not require the user any extra steps to make the content available after import. We could definitely limit which resources are allow

Re: [Pulp-dev] Importers/Exporters

2020-02-21 Thread David Davis
A couple comments. I'm not sure how pulp will be able to export all the extra metadata that comes from Katello as some of it relates to content views. Also, I'm hesitant to have the user export a generic list of pulp hrefs. I think this could be confusing (do users have to supply artifact hrefs to