Puppet pcore resource type definitions are generated using {{puppet generate types}} and ensure resource types are isolated in a single environment. This is needed by the compiler as it needs to compile catalogs on behalf of agents in multiple environments. However, the pops loaders will by default include the pcore resource type loader which can lead to issues like PUP-9602. It also means pcore resource types could be loaded by another application unexpectedly.
For puppet 7, change the default behavior so that pcore resource types are not automatically loaded, and modify puppetserver to opt-into the behavior. Need to research {{puppet script}}.
Puppet pcore resource type definitions are generated using {{puppet generate types}} and ensure resource types are isolated in a single environment. This is needed by the compiler as it needs to compile catalogs on behalf of agents in multiple environments. However, the pops loaders will by default include the pcore resource type loader which can lead to issues like PUP-9602. It also means pcore resource types could be loaded by another application unexpectedly.
For puppet 7, change the default behavior so that pcore resource types are not automatically loaded, and modify puppetserver to opt-into the behavior. Need to research {{puppet script}}.
We may not want to change the default due to bolt and orchestrator
Changing the default behavior would need to be coordinated with puppetserver as well as external tools that interact with the compiler like catalog-diff and puppet-strings. So I'm going to close this as won't fix.