Follow up on this. Looks like this was noticed in 2015 or so and was closed as "wont-fix" https://tickets.puppetlabs.com/si/jira.issueviews:issue-html/PUP-2627/PUP-2627.html The documentation should probably updated to not suggest using the ral resource terminus in this case if it's known to not work...
Aside from that I'm kind of curious now where the ral resource terminus is used where rejecting non-native types is desired. Is this only for the `puppet resource` command? On Wednesday, November 30, 2022 at 8:13:12 AM UTC-8 Sage Imel wrote: > I'm having an issue where attempts to collect exported resources of > defined types fails, when following the instructions here for how to > connect stand alone nodes to puppetdb > https://puppet.com/docs/puppetdb/7/connect_puppet_apply.html#manage-routesyaml > > Very concise example is: > fab01:~# cat example.pp > define example ( > ) { > } > > @@example {"example": > } > > Example <<| |>> > fab01:~# puppet apply --confdir=/opt/cat/puppet/etc/puppet example.pp > Error: Could not find type Example on node fab01.cecs.pdx.edu > > The failure seems rooted in the ral resource indirector, example > routes.yaml: > > --- > apply: > catalog: > terminus: compiler > cache: puppetdb > resource: > terminus: ral > cache: puppetdb > facts: > terminus: facter > cache: puppetdb_apply > > Thanks, > > Sage Imel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/17e5ff64-0413-4199-baf5-f2e3a2871475n%40googlegroups.com.
