Hi @Conan_Kudo and @ikonia
Thanks for taking the time to write. I want to provide a bit of background.
Pulp 3 addresses major problems that were not possible to implement within the Pulp 2 architecture. This overhaul meant that every content plugin had to be written from scratch. For more information about the changes between Pulp 2 and Pulp 3, see About Pulp 3 on the Pulp project site.
Creating these new plugins was prioritized based on what the community used most and was asking for.
From the preliminary data gathered in the 2020 Foreman community survey, as well as the Puppet mini survey, we learned that the Pulp & Katello workflows for Puppet content were rarely used. For Puppet, the Katello functionality did not match the capabilities that were found in tools such as the R10k project. For example, the Puppet Forge v3 API was never implemented in Pulp, and therefore Puppet content management with Katello was limited to the built-in flows. Replacing the deployment script with existing tools like r10k was impossible. R10k has example hooks to flush the Puppetserver cache but Pulp didn’t. Feature-wise, it was very limited.
While currently implementing a Puppet plugin is not planned by the Pulp core team, If there is enough interest in the community in managing Puppet using Pulp & Katello, it is possible to write one. If you’re interested in writing a Puppet plugin, see the Pulp plugin writer’s guide. This then can be incorporated into future Katello releases.
Depending on how you are managing Puppet content, you might find some necessary functionality in the Pulp File plugin.
With regards to OSTree content, there is no plugin currently available for Pulp 3, but there are discussions happening about creating this plugin. Again, if you’re interested in contributing, see the Pulp plugin writer’s guide or get in touch.