Open alexjfisher opened 7 years ago
Perhaps getting the from
catalog from puppetdb can't ever work out that well. :(
https://docs.puppet.com/puppetdb/4.4/api/wire_format/catalog_format_v9.html
PuppetDB receives catalogs from Puppet masters in the following wire format. This format is subtly different from the internal format used by Puppet, so catalogs are converted by the PuppetDB catalog terminus before they are sent.
I think I ran into something similar this while attempting to diff a from-catalog right from puppetdb 4.4 with a to-catalog downloaded from puppetdb 5.1 and living in a file under /tmp.
octocatalog-diff --from-puppetdb --to-catalog /tmp/5_myhost.json --hostname myhost.me.com
BUG: catalog has no data::resources or ::resources array. Please report this.
I notice that in both versions of the puppetdb catalog "resources" is a hash (resources[data] is an array), but in the version used by the puppet agent for the same server "resources" is an array.
Hi! I'm just starting out with the tool and have been trying to use the
--from-puppetdb
option. (Should this option be documented here?)In the above example, the node is already in the
production
environment and running puppet. I would therefore expect there to be no differences. Unfortunately, I get quite a few. I think I could filter them out with someignore
options, but I was planning to use the tool in a CI setup (seeing which nodes will be affected by a change), so I don't think this would be practical.On my servers I'm using CentOS 7 with... puppetserver-2.7.2 puppetdb-4.4.0 (with postgresql 9.6) puppet-agent-1.10.4
I'm running octocatalog-diff 1.4.0 on ruby 2.4.1 via rvm on ubuntu.
Many thanks, Alex