1. 07 Feb, 2017 3 commits
  2. 25 Oct, 2016 1 commit
    • Wyatt Alt's avatar
      (PDB-3071) Log a warning if retired server/port config items are in use. · 9be9a8ac
      Wyatt Alt authored
      It's relatively common for users to miss the retirement of server/port
      when upgrading from versions of PDB that supported it. This has the
      effect of defaulting their server/port to puppetdb:8081, producing agent
      run failures that log a puppetdb hostname different from what they
      believe they've configured.
      
      This patch logs warnings when server and port are detected in the config
      file. I think it would be preferable to remove the defaulting behavior
      and throw an error when server_urls is not present, but I don't have a
      sense of whether anyone relies on the defaulting today.
      9be9a8ac
  3. 10 Oct, 2016 1 commit
    • Wyatt Alt's avatar
      (PDB-3071) Log a warning if retired server/port config items are in use. · c95db47b
      Wyatt Alt authored
      It's relatively common for users to miss the retirement of server/port
      when upgrading from versions of PDB that supported it. This has the
      effect of defaulting their server/port to puppetdb:8081, producing agent
      run failures that log a puppetdb hostname different from what they
      believe they've configured.
      
      This patch logs warnings when server and port are detected in the config
      file. I think it would be preferable to remove the defaulting behavior
      and throw an error when server_urls is not present, but I don't have a
      sense of whether anyone relies on the defaulting today.
      c95db47b
  4. 04 Oct, 2016 1 commit
  5. 03 Oct, 2016 1 commit
  6. 11 Aug, 2016 1 commit
  7. 10 Aug, 2016 1 commit
  8. 03 Aug, 2016 1 commit
  9. 07 Jul, 2016 1 commit
  10. 06 Jul, 2016 1 commit
  11. 23 Jun, 2016 1 commit
  12. 19 Jun, 2016 1 commit
  13. 14 Jun, 2016 1 commit
  14. 09 Jun, 2016 1 commit
  15. 13 May, 2016 1 commit
    • Karel Březina's avatar
      (PE-15587) Set noop flag on a report to true only if all its resource events are noop · b6c2243f
      Karel Březina authored
      This commit improves the algorithm which tries to recognize that puppet run was started with --noop param. Originally, any noop resource event caused that the whole report was marked as noop. However, a noop puppet run would have all resource events in noop state. With this commit, all resource events need to be noop to mark the whole report as noop.
      
      The current implementation is not able to recognize an unchanged noop puppet run since it doesn't contain any events. So, this improvement is just a workaround. To be able to recognize noop puppet runs properly, puppet needs to report in which mode was the run started. This problem is logged as PUP-6294.
      b6c2243f
  16. 21 Apr, 2016 1 commit
    • lafont's avatar
      Add a basic checking of the "query" parameter · 3e46965b
      lafont authored
      To be compatible with Puppet 4.0.0 where recursive types
      are not possible, the type checked here is not accurate.
      Ideally, the type should be:
      
        Variant[String[1], StringTree]
      
      where StringTree is defined (recursively) by:
      
        StringTree = Array[Variant[String, StringTree]]
      3e46965b
  17. 31 Mar, 2016 1 commit
  18. 07 Mar, 2016 1 commit
  19. 16 Feb, 2016 3 commits
  20. 26 Jan, 2016 1 commit
  21. 21 Jan, 2016 1 commit
  22. 13 Jan, 2016 1 commit
  23. 18 Dec, 2015 1 commit
    • Ryan Senior's avatar
      (PDB-2256) Fix terminus bug with large binary catalog data · 0b96f28b
      Ryan Senior authored
      The terminus includes code to help users diagnose the source of data
      that cannot be converted to UTF-8. There are several sources of this,
      but one is having an incorrect (or known) character set for portions of
      the catalog. When this invalid character data is large, it would cause
      the terminus to hang trying to include debugging information.
      
      This patch changes the terminus to only look for the first instance of
      bad data. It will also avoid doing the extra calculations needed for the
      error context unless debug mode is enabled. When not in debug mode there
      should be no impact on performance.
      0b96f28b
  24. 17 Dec, 2015 1 commit
    • Ryan Senior's avatar
      (PDB-2256) Fix terminus bug with large binary catalog data · fef7418b
      Ryan Senior authored
      The terminus includes code to help users determine the source of data
      that cannot be converted to UTF-8. There are several sources of this,
      but one is having an incorrect (or known) character set for portions of
      the catalog. When this invalid character data is large, it would cause
      the terminus to hang trying to include debugging information.
      
      This patch changes the terminus to only look for the first instance of
      bad data. It will also avoid doing the extra calculations needed for the
      error context unless debug mode is enabled. When not in debug mode there
      should be no impact on performance.
      fef7418b
  25. 09 Nov, 2015 1 commit
  26. 03 Nov, 2015 2 commits
  27. 30 Oct, 2015 8 commits
  28. 29 Oct, 2015 1 commit