1. 11 Oct, 2016 1 commit
    • Wyatt Alt's avatar
      (PDB-3058) version 6 reports incorrectly rejected · f309993c
      Wyatt Alt authored
      This was a schema error introduced with the corrective_change feature.
      The main operational impact was that users upgrading from 3.2.x to 4.2
      with enqueued data would have their commands fail on restart.
      This commit corrects the schema to accept v6 reports, and also does a
      bit of test cleanup so we won't have this problem again. Specifically it
      consolidates synthesis of old command versions under the example reports
      namespace and causes test compilation to fail if the synthetic reports
      are invalid.
  2. 06 Jul, 2016 1 commit
  3. 23 Jun, 2016 1 commit
  4. 14 Jun, 2016 1 commit
  5. 16 Feb, 2016 2 commits
  6. 12 Jan, 2016 1 commit
  7. 01 Oct, 2015 1 commit
  8. 29 Sep, 2015 1 commit
  9. 28 Sep, 2015 3 commits
  10. 14 Sep, 2015 1 commit
    • Andrew Roetker's avatar
      (maint) Ensure export queries are lazy · 460712e6
      Andrew Roetker authored
      This commit removes the seq schema validation for the `query->wire`
      functions we use for streaming PuppetDB data to the export data so that
      our export queries are indeed streaming and don't hold all the PuppetDB
      reports in memory.
  11. 26 Aug, 2015 1 commit
  12. 24 Aug, 2015 1 commit
    • Andrew Roetker's avatar
      (PDB-1852) Store the `resources` doc from the new wire-format of reports · a107b41e
      Andrew Roetker authored
      This commit changes PuppetDB's report storage to expect the v6
      wire-format with the resources (instead of resource_events) field and
      stores the resources document as a JSONB column in reports that was
      created in a previous commit's migration addition. This commit updates
      the tests to be more compatible with the new version, removing
      unnecessary fields in the example reports' `resource_events` fields.
  13. 01 Jul, 2015 1 commit
  14. 22 Jun, 2015 1 commit
    • Ryan Senior's avatar
      (PDB-1590) Support two previous versions of all commands (for upgrades) · e3945f38
      Ryan Senior authored
      Note these previous versions are not supported at the API level. The
      intent here is if the user has upgraded from PuppetDB 2.0.0 to 3.0.0 and
      there are still persisted messages in the queue (POSTed, but not
      processed) those messages should be consumable by PuppetDB 3.0.0.
      This commit takes a previous version of the command and upgrades it,
      filling in anything missing, changing the names of keys as necessary to
      conform it to the current (supported) command version.
  15. 18 May, 2015 1 commit
    • Russell Mull's avatar
      (PDB-1487) Add producer_timestamp to store-report · 3ac87dbb
      Russell Mull authored
      The store-report command contains start_time and end_time, but those
      are generated on the agent. This adds a producer_timestamp field to the
      command, which is generated on the master. It can then be reliably
      compared with the producer_timestamp on the deactivate-node command.
  16. 02 Apr, 2015 1 commit
    • Ken Barber's avatar
      (PDB-1228) Multiple fixes to get expansion working · 77592b59
      Ken Barber authored
      * Remove concept of expand as a paging parameter
      * Use maptrans and collapse some more munge funcs
      * More schema validation work
      * Fix where matching clause ambiguity
      * Get export/import working
      * Ensure url-prefix is used in expanded href/data blocks
      * Restrict edges query to active nodes
      * Fix hash_debug to use the new format
      * Convert remaining expressions to use honeysql
      * Many test fixes
      * Return iso8601 timestamps with row_to_json for PG 9.3
      * Remove reports/<hash>/events projection restriction
      * catalogs are only returned for active nodes to match the rest of the endpoints
      * Upgrade to latest honeysql and use cast formatting
      Signed-off-by: default avatarKen Barber <ken@bob.sh>
  17. 05 Mar, 2015 1 commit
    • wkalt's avatar
      (PDB-1192) add metrics and logs support · 5abc90eb
      wkalt authored
      This adds two fields, logs and metrics, to the reports response to contain
      logs and metrics passed from Puppet in the terminus. This is part of the ongoing
      work to retire consoleDB.
  18. 26 Feb, 2015 1 commit
    • Andrew Roetker's avatar
      (PDB-1229) Use schema for reports validation · 0e7ff6b3
      Andrew Roetker authored
      Prior to this commit we were using validation.clj, a home-baked version
      of prismatic/schema  to validate report maps. This commit removes
      validation.clj and changes reports to use prismatic/schema for
      validation instead.
  19. 18 Feb, 2015 1 commit
    • wkalt's avatar
      (PDB-1177) add noop flag to reports · 510e3ad1
      wkalt authored
      This adds a "noop" field to the reports object, which is a boolean flag
      indicating whether the run producing the report was a --noop.
  20. 10 Feb, 2015 1 commit
    • wkalt's avatar
      (PDB-698) Convert from dashes to underscores in API commands and responses · fde50cbd
      wkalt authored
      This patch changes our API commands and responses to use underscores instead of
      dashes, which will make it easier to interface with PDB using languages like
      javascript and python.
      This bumps the version of replace-facts, replace-catalog, and store-report,
      and changes our subquery operators to use underscores as well.
  21. 28 Jan, 2015 1 commit
  22. 07 Jan, 2015 1 commit
    • Andrew Roetker's avatar
      (PDB-840) Retire deprecated commands · 319f654c
      Andrew Roetker authored
      This commit retires all of the previously deprecated commands and
      removes all the associated support code for these commands, such as
      validation of reports/catalogs for the deprecated versions. This commit
      also updatees al the unit/integration tests to use the non-retired
      versions of these commands and removes test code we no longer use.
  23. 25 Sep, 2014 1 commit
  24. 05 Sep, 2014 1 commit
    • Ken Barber's avatar
      (PDB-843) Namespace changes for source and test code · 51a10d35
      Ken Barber authored
      Our engineering org has decided to use puppetlabs.<library_name> as a standard
      across our Clojure projects, this patch lines us up with that standard.
      This also moves the libraries in com.puppetlabs.* into puppetlabs.puppetdb also,
      to avoid collisions with any other project. These files were designed to be
      pulled out of PuppetDB one day, but for now we've moved them all into the same
      We also have re-aligned our tests to be more standard, adopting the namespace-test
      convention. This aids with editors also, as now we can switch easily between src
      and test.
      All the various places that care about this change have been changed, including
      SysV scripts, systemd definitions and the command line utilies that are responsible
      for launching PuppetDB, since we now have puppetlabs.puppetdb.core as the main
      entry point. boostrap.cfg, and logback.xml have been changed also.
      Since we were changing a lot of the (ns ..) blocks across all files we took the
      opportunity to clean them up. :use is now now longer used (excuse the pun).
      Comments at the top of libraries are now in the ns doctstring also.
      The test-resources directory has also been aligned with the new namespaces and
      tests are now pointing at the new layout.
      For backwards compatibility, we've kept the old namespace pinned for JMX & ActiveMQ
      queues, since these are still required for our stable API commitments. In the future
      we'll have to fix this.
      The concurrent.clj code has been removed, I found it wasn't used so removed it.
      Signed-off-by: default avatarKen Barber <ken@bob.sh>
  25. 08 May, 2014 1 commit
  26. 25 Mar, 2014 1 commit
  27. 10 Jan, 2014 1 commit
    • Ken Barber's avatar
      PDB-279 Sanitize report imports · a96c53e8
      Ken Barber authored
      Previously we had a bug PDB-85 that caused our exports on 1.5.x to fail. This
      has been fixed, but alas people are trying to import those broken dumps into
      1.6.x and finding it doesn't work.
      This patch sanitizes our imports by only using select keys from the reports
      model and dropping everything else.
      Signed-off-by: default avatarKen Barber <ken@bob.sh>
  28. 14 Nov, 2013 1 commit
  29. 18 Oct, 2013 1 commit
  30. 13 Sep, 2013 2 commits
  31. 28 Aug, 2013 2 commits
  32. 13 Aug, 2013 1 commit
  33. 25 Jul, 2013 3 commits
    • Nate Wolfe's avatar
      (PE-959) Save resource event file/line properties · 6aa7d847
      Nate Wolfe authored
      Prior to this commit, the file and line properties that exist on a
      resource event were not being saved down to PuppetDB during report
      processing. This commit changes that so we can show that information
      in Burgundy.
    • Chris Price's avatar
      Introduce v2 of store-report command · 68abcca4
      Chris Price authored
    • Chris Price's avatar
      Updated store-report command to a multimethod · a71b024d
      Chris Price authored
      We will need to support multiple versions of the store-report
      command for Burgundy since we're changing the wire format.
      This commit simply re-works the existing store report command
      to use a multimethod, and introduces v1 of the multimethod.
      This commit does not introduce a v2 implementation of the
      multimethod yet.