Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Wyatt Alt Scope Change Category: Found Scope Change Reason: critical burnside bug Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Susan McNerney Scope Change Reason: critical burnside Major bug in impending release. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema My notes so far: We catch any errors raised in our handler's call method (and raise if there's any issue anywhere in processing) in 'network/http/api/indirected_routes' where both handlers for exceptions explicitly set the content type to "text/plain" and pass the exception message through to the message body (via Puppet::Network::HTTP::Response#respond_with, Puppet::Network::HTTP::RackREST#set_response, Rack::Response#write). Exceptions outside of the handler's call (issues with the rack app itself) return a 500 via a substantively similar, but different code path, in 'network/http/rack'. Setting the content type properly, retrieving the requested format (defaulting to P JSON), and rendering the content accordingly – similar to our code for indirector paths should work. That approach should work assuming the Exception/message instance that we pass into the formatter chooser has supported_formats and to_pson defined that list pson as a valid serialization format and can serialize to the schema linked in the description respectively. Fantastically, nearly the exact same described beast exists in 'network/http/error' and conveniently its subclasses are the exceptions we're throwing all over the place. Given the above I think we can implement this by: Update do_http_control_exception to pass the exception it receives to the formatter and pass the properly formatted response on to the request. Update the do_exception handler to do similar after first wrapping the passed exception in a Puppet::Network::HTTP::Error::HTTPError:: HTTPBadRequestError. Update the 500 error handling to be substantively similar to the #2 above but first wrapping any exceptions in a Puppet::Network::HTTP::Error::HTTPError::HTTPServerError, natch. Gotcha: the HTTP error classes don't implement a supported_formats method, so we either need to implement that on their base class or rework/write our own version of accepted_response_formatter_for/accepted_response_formatter_or_pson (we may have to roll our own anyways/extract that functionality out for the 500 processing since that happens in the Rack app outside of an indirected route). Open question: 1. Accept header requirements and pson vs json: accepted_response_formatter_for requires an accepts header to be specified by the client. Is that the correct level of pedantry? accepted_response_formatter_or_pson defaults to pson if the accepts header isn't present, which is basically json, which seems fine... But pson serialization is implemented for indirector classes and/or resources while the current HTTP exceptions have implemented json serialization. I'm spacing on when and why its okay to do one and not the other (see if there's docs for that).
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Susan McNerney commented on PDB-2581 Re: PDB connection pool size defaults to 10 instead of 25 and cannot be configured Will be discussing in the burnside leads triage 9:30am friday in Hyde; in the meantime, Wyatt will move forward on the PDB side. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Susan McNerney Fix Version/s: PDB 4.0.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Susan McNerney Labels: burnside-ss tcse Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Wyatt Alt Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Wyatt Alt Sprint: PuppetDB 2016-04-06 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Ryan Gard QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Ryan Gard QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Ryan Gard QA Contact: Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Change By: Nick Walker Affects Version/s: PDB 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2581) PDB connection pool size defaults to 10 instead of 25 and cannot be configured
Title: Message Title Nick Walker created an issue PuppetDB / PDB-2581 PDB connection pool size defaults to 10 instead of 25 and cannot be configured Issue Type: Bug Assignee: Unassigned Created: 2016/03/31 5:30 PM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem I'm seeing 20 connections to postgresl from puppetdb pe-postgres=# select datname, count(*) From pg_Stat_activity where datname = 'pe-puppetdb' group by datname; datname | count -+---
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Henrik Lindberg commented on PUP-1974 Re: Theme: Sensitive Data in Catalogs Eric Sorenson yes, totally agree - that is by far the best option. I discussed that with Adrien Thebo a while ago - we did talked briefly about letting the Encrypted type describe the encryption method and value - thus supporting both actual encrypted value, and late binding handle based encryption simply by choice of encryption-method. Naturally the value in the handle based case is the handle/key (in clear text), but when decrypted it is resolved into the secret value via the remote service indicated by the method. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2547) Add in new clj-i18n scaffolding to PuppetDB
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2547 Add in new clj-i18n scaffolding to PuppetDB Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Glenn Sarti assigned an issue to Ryan Gard Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Glenn Sarti Assignee: qa Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Eric Sorenson commented on PUP-1974 Re: Theme: Sensitive Data in Catalogs I read through the linked tickets but didn't see a mention of an alternative approach that seems promising to me - as Adrien Thebo described it elsewhere: Another option for dealing with sensitive data in the catalogs is to either strip out sensitive information in the catalog and replace it with a reference that the agent cant look up, or never store the sensitive information in the catalog and only ship around catalogs with references to secure information. To complement this we would need a concept of a security or secret provider for the agent. A secret provider could be something like Conjur, or an encrypted sidecar file that ships along with the catalog with the secrets that's encrypted with something like the agent's SSL public key. This kind of late-binding secret lookup is consistent with use-cases where the data is both secret and ephemeral, so embedding it in a (persistent, cached) catalog is doubly wrong. Even if it's not ephemeral, the ability to query and inject secret data at catalog application time would be highly useful. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash After a lengthy discussion between Thomas Hallgren, Peter Huene and Henrik Lindberg we decided that the best option is to encode empty array and hash as follows: Array[0,0] Hash[0,0] And, that it is an error to attempt to create a typed empty container - i.e. the following is illegal: Array[Integer, 0, 0] Hash[String, String, 0, 0] As that removes the ambiguities concerning comparing empty typed container. Add Comment
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Glenn Sarti assigned an issue to qa Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Glenn Sarti Status: Ready for CI Test Assignee: Glenn Sarti qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Glenn Sarti commented on PUP-5588 Re: Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Artifacts available at; http://builds.puppetlabs.lan/puppet-agent/d4f82e31005ec730bf2fc51cc9c996f11f3908b1/artifacts/windows/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2547) Add in new clj-i18n scaffolding to PuppetDB
Title: Message Title Andrew Roetker commented on PDB-2547 Re: Add in new clj-i18n scaffolding to PuppetDB So looks like the clj-i18n repo https://github.com/puppetlabs/clj-i18n is private, we probably need this open-source if we want to use this in PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2556) Tag the release and create packages (PDB 0.1.0)
Title: Message Title
Melissa Stone updated an issue
PuppetDB / PDB-2556
Tag the release and create packages (PDB 0.1.0)
Change By:
Melissa Stone
(Initial planned release date: 2016- 03 04 - 23 07 )Tag and create packages * Developer provides the SHA - [~ryan.senior] - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb) * checkout the sha* Make sure you are about to tag the correct thing * Create the tag e.g.) git tag -s -u {GPG key} -m "1.7.3" 1.7.3* You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.* DO NOT push the tag to the repo, keep it local only * `git describe` will show you the tag. Make sure you're building what you think you're building. * Make sure you look over the code that has changed since the previous release so we know what's going out the door. * run `rake package:implode package:bootstrap pl:jenkins:uber_build` when you've verified what version you're building (this uses the latest version of the packaging repo to build the packages). * If this is a puppet release, you have to build the windows msi. This is done using jenkins jobs on jenkins-legacy. You have to make sure you're targeting the correct versions of hiera, facter and puppet. * [~morgan] please add a comment with location of packages.For puppet, don't forget the msi packages. This usually comes after other smoke testing is going well since it does require the tag to be pushed live.Dependencies: * Every ticket before this except for release notes.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2561) Docs pushed (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2561 Docs pushed (puppet-client-tools 1.0.0) Change By: Melissa Stone Summary: Docs pushed ( PDB 0. puppet-client-tools 1.0 .0 ) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2561) Docs pushed (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2561 Docs pushed (puppet-client-tools 1.0.0) Change By: Melissa Stone (Initial planned release date: 2016- 03 04 - 23 07 )Push the documentation updates to docs.puppetlabs.com.Dependencies: * Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2559) Push tag (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2559 Push tag (puppet-client-tools 1.0.0) Change By: Melissa Stone Summary: Push tag ( PDB 0. puppet-client-tools 1.0 .0 ) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2559) Push tag (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2559 Push tag (puppet-client-tools 1.0.0) Change By: Melissa Stone (Initial planned release date: 2016- 03 04 - 23 07 )The development team is responsible for updating the stable/master branches as necessary.This will be done after the version bump in version.rb.Dependencies: * Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2560) Packages pushed (PDB 0.1.0)
Title: Message Title Melissa Stone assigned an issue to Ryan McKern PuppetDB / PDB-2560 Packages pushed (PDB 0.1.0) Change By: Melissa Stone Assignee: Melissa Stone Ryan McKern Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2560) Packages pushed (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2560 Packages pushed (puppet-client-tools 1.0.0) Change By: Melissa Stone Summary: Packages pushed ( PDB 0. puppet-client-tools 1.0 .0 ) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2560) Packages pushed (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2560 Packages pushed (puppet-client-tools 1.0.0) Change By: Melissa Stone (Initial planned release date: 2016- 03 04 - 23 07 )Push packages * run `rake pl:jenkins:uber_ship`* You will need the keys to the castle (aka the passphrase) for this to work.* Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms.* Get a *second set of RelEng eyes* on the packages that are about to be shipped to make sure everything looks a-okay.* If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file.* If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.Dependencies: * Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2555) Prepare long form release notes and short form release story (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2555 Prepare long form release notes and short form release story (puppet-client-tools 1.0.0) Change By: Melissa Stone (Initial planned release date: 2016- 03 04 - 23 07 )Collaborating with product for release storyDependencies: * Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2559) Push tag (PDB 0.1.0)
Title: Message Title Melissa Stone assigned an issue to Ryan McKern PuppetDB / PDB-2559 Push tag (PDB 0.1.0) Change By: Melissa Stone Assignee: Melissa Stone Ryan McKern Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2556) Tag the release and create packages (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2556 Tag the release and create packages (puppet-client-tools 1.0.0) Change By: Melissa Stone Summary: Tag the release and create packages ( PDB 0. puppet-client-tools 1.0 .0 ) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2556) Tag the release and create packages (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone assigned an issue to Ryan McKern PuppetDB / PDB-2556 Tag the release and create packages (puppet-client-tools 1.0.0) Change By: Melissa Stone Assignee: Melissa Stone Ryan McKern Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2555) Prepare long form release notes and short form release story (puppet-client-tools 1.0.0)
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2555 Prepare long form release notes and short form release story (puppet-client-tools 1.0.0) Change By: Melissa Stone Summary: Prepare long form release notes and short form release story ( PDB 0. puppet-client-tools 1.0 .0 ) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2549) puppet-client-tools 1.0.0 2016-03-23 Release
Title: Message Title Melissa Stone commented on PDB-2549 Re: puppet-client-tools 1.0.0 2016-03-23 Release cc/ Ryan Senior Michael Stahnke Andrew Roetker so, it looks like the blocking things outlined in Mike's email have all happened. We should be ready to release puppet-client-tools now. I have conflicting version information that I would like clarified. Are we releasing puppet-client-tools 1.0.0 or 0.1.0? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2549) puppet-client-tools 1.0.0 2016-03-23 Release
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2549 puppet-client-tools 1.0.0 2016-03-23 Release Change By: Melissa Stone Summary: puppetdb puppet - cli client-tools 1.0.0 2016-03-23 Release Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1294) Windows facter.rb lookup of libfacter has hard-coded layout assumptions
Title: Message Title Michael Smith updated an issue Facter / FACT-1294 Windows facter.rb lookup of libfacter has hard-coded layout assumptions Change By: Michael Smith Fix Version/s: FACT 3.1.7 Fix Version/s: FACT 3.1.6 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1294) Windows facter.rb lookup of libfacter has hard-coded layout assumptions
Title: Message Title Josh Cooper commented on FACT-1294 Re: Windows facter.rb lookup of libfacter has hard-coded layout assumptions Kylo Ginsberg, Michael Smith This change is in facter@stable, so I'm assuming it will go out in 3.1.6 instead of 3.1.7? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Nate McCurdy created an issue Puppet / PUP-6115 The instructions for cleaning a Windows node's certificate are wrong Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Attachments: windows.png Created: 2016/03/31 10:53 AM Priority: Normal Reporter: Nate McCurdy On a windows node, if there's some problem with the node's certificate during a puppet agent run (such as a cert already existing on the master with the same name) then instructions are printed to clean the cert on the master and the agent node. The command to delete the certificate in Windows is wrong. See the following screenshot: The 2 problems are: 'certs' is missing from the path Back slashes should be used rather than forward slashes.
Jira (PUP-1258) Puppet should be filesystem ACL aware / do not manage mode unless explicitly present
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-1258
Puppet should be filesystem ACL aware / do not manage mode unless explicitly present
Change By:
Eric Sorenson
Puppet should be aware of when filesystem ACLs are present on a file, and behave just slightly differently on said files.I've seen other feature requests asking to support filesystem ACLs and this isn't that. It'll be best to explain with an example scenario.Lets say you have the file '/foo/bar' with an ACL 'mask::rwx' and 'group::r-x'.Now lets also say you have the resource {code}file {'/foo/bar': mode => '0755'}{code}When you do a `stat` call to get the permissions of the file, they're going to show up as '0775', even though the group does not have write permission. Because of this, puppet is going to go an do a `chmod 0755` on the file, which will change the ACL mask to 'mask::r-x'. Not the intended result.Now you might argue that you shouldn't manage the file permissions with a file resource if the file has an ACL on it. And I'm on the fence whether this the proper answer. However there's another scenario where you might do { { code} file {'/foo': ensure => directory, recurse => true, mode => '0755'} {code } } and it goes and screws up the ACL of any files in that directory.While I think full ACL support is another matter entirely, I think that when puppet makes the `stat` call to get the permissions on the file, if it detects the file has an ACL on it, it should inspect the permissions with `getfacl`, and adjust them with `setfacl` if necessary (again, *only* for the primary user/group/other attributes, not full ACL support).The only other solution I can think of is for puppet to get full ACL support, and when puppet detects a file with an ACL on it, it creates a `facl` resource to manage the permissions instead of the file type managing the permission itself.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-1258) Puppet should be filesystem ACL aware / do not manage mode unless explicitly present
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-1258
Puppet should be filesystem ACL aware / do not manage mode unless explicitly present
Change By:
Eric Sorenson
Puppet should be aware of when filesystem ACLs are present on a file, and behave just slightly differently on said files.I've seen other feature requests asking to support filesystem ACLs and this isn't that. It'll be best to explain with an example scenario.Lets say you have the file '/foo/bar' with an ACL 'mask::rwx' and 'group::r-x'.Now lets also say you have the resource { { code} file {'/foo/bar': mode => '0755'} . {code } } When you do a `stat` call to get the permissions of the file, they're going to show up as '0775', even though the group does not have write permission. Because of this, puppet is going to go an do a `chmod 0755` on the file, which will change the ACL mask to 'mask::r-x'. Not the intended result.Now you might argue that you shouldn't manage the file permissions with a file resource if the file has an ACL on it. And I'm on the fence whether this the proper answer. However there's another scenario where you might do {{file {'/foo': ensure => directory, recurse => true, mode => '0755'} }} and it goes and screws up the ACL of any files in that directory.While I think full ACL support is another matter entirely, I think that when puppet makes the `stat` call to get the permissions on the file, if it detects the file has an ACL on it, it should inspect the permissions with `getfacl`, and adjust them with `setfacl` if necessary (again, *only* for the primary user/group/other attributes, not full ACL support).The only other solution I can think of is for puppet to get full ACL support, and when puppet detects a file with an ACL on it, it creates a `facl` resource to manage the permissions instead of the file type managing the permission itself.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-1258) Puppet should be filesystem ACL aware / do not manage mode unless explicitly present
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-1258
Puppet should be filesystem ACL aware / do not manage mode unless explicitly present
Change By:
Eric Sorenson
Puppet should be aware of when filesystem ACLs are present on a file, and behave just slightly differently on said files.I've seen other feature requests asking to support filesystem ACLs and this isn't that. It'll be best to explain with an example scenario.Lets say you have the file '/foo/bar' with an ACL 'mask::rwx' and 'group::r-x'.Now lets also say you have the resource ` {{ file {'/foo/bar': mode => '0755'} ` . }} When you do a `stat` call to get the permissions of the file, they're going to show up as '0775', even though the group does not have write permission. Because of this, puppet is going to go an do a `chmod 0755` on the file, which will change the ACL mask to 'mask::r-x'. Not the intended result.Now you might argue that you shouldn't manage the file permissions with a file resource if the file has an ACL on it. And I'm on the fence whether this the proper answer. However there's another scenario where you might do ` {{ file {'/foo': ensure => directory, recurse => true, mode => '0755'} ` }} and it goes and screws up the ACL of any files in that directory.While I think full ACL support is another matter entirely, I think that when puppet makes the `stat` call to get the permissions on the file, if it detects the file has an ACL on it, it should inspect the permissions with `getfacl`, and adjust them with `setfacl` if necessary (again, *only* for the primary user/group/other attributes, not full ACL support).The only other solution I can think of is for puppet to get full ACL support, and when puppet detects a file with an ACL on it, it creates a `facl` resource to manage the permissions instead of the file type managing the permission itself.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6114) Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type
Title: Message Title Michael Stahnke moved an issue Puppet / PUP-6114 Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type Change By: Michael Stahnke Affects Version/s: puppet-agent 1.4.1 Workflow: Release Engineering Scrum Team Workflow Key: PA PUP - 272 6114 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://
Jira (PUP-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Eric Sorenson commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup There is a lot of conversation on the ticket but if I understand correctly, this last section seems quite reasonable to me The dot-access notation is established and doing something different is just annoying. If we come up with a better thing in the future we can deal with that then. We should support dotted notation in both the lookup CLI, and in the lookup function. Users that want a verbatim lookup of a key with a dot in the key needs to quote it. In order to make the dotted notation more of a general feature, we should also add an access function that applies to any hash or array. It should have an API that allows users to either use a single string to describe the access, or an array of keys. I always have nagging questions about PQL as it relates to this kind of nested data but I read through the docs and checked with the team and the dot syntax should be consistent (ping Kenneth Barber just in case). So from me. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@goog
Jira (PUP-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Henrik Lindberg commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup Ping Eric Sorenson - are you ok with the potential breakage? Given that we still have the lookup feature-set as experimental and that it is unlikely that it will affect more than a handful of early adopters I am in favor of making the change. (It is the other way around - those that try out the new functionality is instead complaining that it is inconsistent). Thomas Hallgren the --access CLI option is off the table as the dot notation would be directly supported. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5965) Add 'new instance' operation
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5965 Add 'new instance' operation Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5965) Add 'new instance' operation
Title: Message Title Thomas Hallgren commented on PUP-5965 Re: Add 'new instance' operation Merged to master at d5b65c6. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5965) Add 'new instance' operation
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5965 Add 'new instance' operation Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6077) puppet commands fail from default users dir on windows 2k8
Title: Message Title Jeff Sparrow assigned an issue to Rob Reynolds Puppet / PUP-6077 puppet commands fail from default users dir on windows 2k8 Change By: Jeff Sparrow Assignee: Jeff Sparrow Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2577) Puppet master changes are causing our rspec tests to fail
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-2577 Puppet master changes are causing our rspec tests to fail Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5965) Add 'new instance' operation
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5965 Add 'new instance' operation Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2124) Please support some database besides PostgresQL
Title: Message Title Kenneth Barber commented on PDB-2124 Re: Please support some database besides PostgresQL Johnson Earls aah, so you work for Oracle, and PostgreSQL is a no-no for competitive reasons, hence why Larry needs to sign off on it. The interfaces for storeconfigs and facts_terminus are just termini for the indirector interfaces which are written in ruby today ... there is some documentation here: https://docs.puppetlabs.com/puppet/latest/reference/indirection.html You can also look at the puppetdb source for examples on the interface: https://github.com/puppetlabs/puppetdb/tree/master/puppet/lib/puppet/indirector Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-773) Add primary keys to 'edges' and 'resource_events'
Title: Message Title Robert M. Wysocki commented on PDB-773 Re: Add primary keys to 'edges' and 'resource_events' Wanted to set up logical replication using pg_logical (native to PostgreSQL). Run into the same issue. It was possible to use REPLICA IDENTITY for few of the tables missing PRIMARY KEYs, but it wasn't possible to resource_events. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
