{"push_id":946355629,"size":1,"distinct_size":1,"ref":"refs/heads/PUP-917/master/report_cached_catalog","head":"665f10363fce1439f15e21a26ae901206041a760","before":"1c7812326e416a05dda7abb8695f95adbc03783b","commits":[{"sha":"665f10363fce1439f15e21a26ae901206041a760","author":{"email":"7ea09030d14c1944151c3d88e79ac21e9459bec8@puppetlabs.com","name":"Will Hopper"},"message":"(PUP-917) Identify in the report why a cached catalog was used\n\nCurrently, the agent run report does not provide any information\non whether or not a cached catalog was used. This can make it\ndifficult to discover that a newly updated manifest is failing,\nas Puppet will fall back to a working cached catalog and succeed,\ncausing the report status to be marked as successful.\n\nThere are two ways a cached catalog may be used: by running the agent\nwith the `--use_cached_catalog` option, or by a catalog failing to\ncompile on the master, causing the agent to automatically fall back to\na cached catalog as long as the `usecacheonfailing` setting is set.\n\nThis commit adds the `cached_catalog_status` field to Puppet::Transaction::Report,\nwith possible values 'not used', 'used because --use_cached_catalog was\nset' and 'used because new catalog failed to compile and\nusecacheonfailure was true'.","distinct":true,"url":"https://api.github.com/repos/whopper/puppet/commits/665f10363fce1439f15e21a26ae901206041a760"}]}