Re: [Pulp-list] pulpcore 3.3.0 and pulp_file 0.3.0 are Generally Available
Here is another highlight for pulp_installer 3.3.0 [1]: * Added support for RHEL8 & CentOS 8 [2] [1] https://github.com/pulp/pulp_installer/releases/tag/3.3.0 [2] https://pulp.plan.io/issues/6259 On Thu, Apr 16, 2020 at 10:04 AM Tatiana Tereshchenko wrote: > Pulpcore 3.3.0 [0] and pulp_file 0.3.0 [1] have been released. For a list > of all changes, please check the changelogs for pulpcore [2] and pulp_file > [3]. Here are some highlights: > * Import/export of repository versions (tech preview) > * Repository version repairing (tech preview) [4] > * S3 is now fully supported and no longer a tech preview > * Various bugfixes and performance improvements > > The only backwards incompatible change [5] is: > * Exporting now requires ALLOWED_EXPORT_PATHS setting. > > # Installation and Upgrade > > Users should use the 3.3.0 release of pulp_installer (previously known as > ansible-pulp) [6] to install or upgrade their installations. This version > of the installer will check compatibility of all installed plugins with > pulpcore 3.3. The installer will abort if any plugin is incompatible. > > # Plugin API > > Plugin writers can see the plugin API changelog here [7]. > There were a couple backwards incompatible changes [8]: > * One is about Exporter (you are not affected unless you have already > started integrating with it). > * The other one makes it the responsibility of a plugin to check the > duplicated content in a repository version. Pulpcore provides validation > methods to do so. See the pulp_file example [9]. > > And in keeping with the recommended strategy to pin plugins to a 3.y > version of pulpcore, plugins should release compatibility releases with 3.3 > as soon as they can. We recommend using "pulpcore>=3.3,<3.4". > > [0] https://pypi.org/project/pulpcore/3.3.0/ > [1] https://pypi.org/project/pulp-file/0.3.0/ > [2] https://docs.pulpproject.org/changes.html#id1 > [3] https://pulp-file.readthedocs.io/en/0.3.0/changes.html#id1 > [4] > https://docs.pulpproject.org/workflows/repairing-repository-versions.html > [5] https://docs.pulpproject.org/changes.html#deprecations-and-removals > [6] https://github.com/pulp/pulp_installer/releases/tag/3.3.0 > [7] https://docs.pulpproject.org/en/3.3.0/changes.html#plugin-api > [8] https://docs.pulpproject.org/changes.html#id50 > [9] > https://github.com/pulp/pulp_file/commit/dc6acb9d60a1d3aa61ff4def99cc12ddd9981076 > ___ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulpcore 3.3.0 and pulp_file 0.3.0 are Generally Available
Pulpcore 3.3.0 [0] and pulp_file 0.3.0 [1] have been released. For a list of all changes, please check the changelogs for pulpcore [2] and pulp_file [3]. Here are some highlights: * Import/export of repository versions (tech preview) * Repository version repairing (tech preview) [4] * S3 is now fully supported and no longer a tech preview * Various bugfixes and performance improvements The only backwards incompatible change [5] is: * Exporting now requires ALLOWED_EXPORT_PATHS setting. # Installation and Upgrade Users should use the 3.3.0 release of pulp_installer (previously known as ansible-pulp) [6] to install or upgrade their installations. This version of the installer will check compatibility of all installed plugins with pulpcore 3.3. The installer will abort if any plugin is incompatible. # Plugin API Plugin writers can see the plugin API changelog here [7]. There were a couple backwards incompatible changes [8]: * One is about Exporter (you are not affected unless you have already started integrating with it). * The other one makes it the responsibility of a plugin to check the duplicated content in a repository version. Pulpcore provides validation methods to do so. See the pulp_file example [9]. And in keeping with the recommended strategy to pin plugins to a 3.y version of pulpcore, plugins should release compatibility releases with 3.3 as soon as they can. We recommend using "pulpcore>=3.3,<3.4". [0] https://pypi.org/project/pulpcore/3.3.0/ [1] https://pypi.org/project/pulp-file/0.3.0/ [2] https://docs.pulpproject.org/changes.html#id1 [3] https://pulp-file.readthedocs.io/en/0.3.0/changes.html#id1 [4] https://docs.pulpproject.org/workflows/repairing-repository-versions.html [5] https://docs.pulpproject.org/changes.html#deprecations-and-removals [6] https://github.com/pulp/pulp_installer/releases/tag/3.3.0 [7] https://docs.pulpproject.org/en/3.3.0/changes.html#plugin-api [8] https://docs.pulpproject.org/changes.html#id50 [9] https://github.com/pulp/pulp_file/commit/dc6acb9d60a1d3aa61ff4def99cc12ddd9981076 ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Please be aware that there is a bug in dynaconf 2.2 with how settings are merged[0]. I recommend upgrading it to dynaconf 3.0.0rc1 for best results when configuring authentication backends in pulp. [0] https://pulp.plan.io/issues/6244 [1] https://pypi.org/project/dynaconf/3.0.0rc1/ On Wed, Apr 15, 2020 at 7:02 PM Dennis Kliban wrote: > Pulp 3 does not currently support multiple users. We are planning to add > support for RBAC in the near future. However, I don't have a concrete > timeline for that. With all that said, you still can configure the web > server to perform authentication[0]. In this case Pulp will stop performing > authentication and will simply look for a WSGI environment variable that > contains the username. > > [0] > https://docs.pulpproject.org/installation/authentication.html#webserver-auth > [1] > https://docs.pulpproject.org/settings.html?highlight=remote_user#remote-user-environ-name > > On Wed, Apr 15, 2020 at 3:19 PM Bin Li (BLOOMBERG/ 120 PARK) < > bli...@bloomberg.net> wrote: > >> >> I am thinking to configure nginx with ldap authentication, but I couldn't >> find a way to interact with the api. Does pulpcore-client work with ldap >> authentication? Has anyone made httpie work with ldap? >> >> Thanks >> ___ >> Pulp-list mailing list >> Pulp-list@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-list > > ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
