Jira (BOLT-598) facter task error
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-598 facter task error Issue Type: Bug Assignee: Unassigned Created: 2018/06/15 4:53 PM Priority: Normal Reporter: Cas Donoghue I was testing running task over PCP and I noticed some issues with facter/facter_task on PE nodes. This could be an issue with how I am setting up test environment, maybe an older version is being set up? After setting up PE (from pe-console-ui test setup) pe-console-ui/acceptance$ rake setup:vmpool Try to run facter task with bolt cas@cas-ThinkPad-T460p:~/working_dir/BOLT-597$ bolt task run facter -n pcp://y9soexya9vtg02g.delivery.puppetlabs.net --configfile ./bolt.yaml Started on y9soexya9vtg02g.delivery.puppetlabs.net... Failed on y9soexya9vtg02g.delivery.puppetlabs.net:
Jira (BOLT-597) Bolt sends invalid _task key to orchestrator
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-597 Bolt sends invalid _task key to orchestrator Issue Type: Bug Assignee: Unassigned Created: 2018/06/15 2:58 PM Priority: Critical Reporter: Alex Dreyer Bolt sends the task to key to orchestrator when running tasks which makes the request invalid. Bolt should strip _ keys from the parameters before sending requests to orchestrator. In the future '' will have to be handled specially when appropriate for orchestrator Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names
Title: Message Title Amy Lazarte commented on PUP-8942 Re: Support issuing certificates with IP Address Subject Alternative Names As it turns out, we need to input a string into the ruby bindings for OpenSSL, and that string expects a colon separator. However, it appears to still work with ipv6 with that colon separator. For that reason, I'm thinking we should probably not change to using = as a separator. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8396) Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called
Title: Message Title Adam Bottchen commented on PUP-8396 Re: Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called Branan Riley I rebased it today, so I flipped this back. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-581) Evaluate top 100 modules
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: Alex Dreyer Download the top ~100 modules on forge and examine the manifests to estimate how much code reuse "Apply from Plans" will enable.How many use bare facts or are all facts accessed through $::facts? How many include providers?How many include types?Which core types and providers are most common? How many modules just use File/Service/Exec?How many include non-autoloader manifests? IE something other than a class or defined type at top scope. Are these even allowed in puppet 6. What facts to they use?What facts do they use for provider suitability? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (PDB-3946) Allow for optional JMX prefixes for metrics
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-3946 Allow for optional JMX prefixes for metrics Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2018/06/15 11:02 AM Priority: Normal Reporter: Zachary Kent If we were to allow JMX monitors to be prefixed we would be able to monitor multiple Java processes and be able to make sense of which logs belong to which process. This could be useful if running multiple PDBs on the same JVM. Add Comment This
Jira (PDB-3945) [SPIKE] see what is involved in moving PDB CI away from multi-stage builds in Jenkins
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-3945 [SPIKE] see what is involved in moving PDB CI away from multi-stage builds in Jenkins Issue Type: Improvement Assignee: Unassigned Created: 2018/06/15 10:41 AM Priority: Normal Reporter: Zachary Kent The current setup for PDB in Jenkins uses multi-stage builds. This could potentially be changed to use the build trigger plugin which would allow us to trigger jobs needed for certain pipelines in sequence. This change would help to make the PDB ci-job-configs code easier to understand and allow more fine grain control over rerunning jobs when they fail. Look at the Server team's ci-job-configs for examples of how this can be accomplished. Add Comment
Jira (PDB-3917) Stop sed-ing project file for tests, and unify test dep handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3917 Stop sed-ing project file for tests, and unify test dep handling Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3917) Stop sed-ing project file for tests, and unify test dep handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3917 Stop sed-ing project file for tests, and unify test dep handling Change By: Rob Browning Fix Version/s: PDB 5.1.6 Fix Version/s: PDB 6.0.0 Fix Version/s: PDB 5.2.3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-503 Use local config automatically to embed bolt in a project Change By: Cas Donoghue Assignee: Alex Dreyer Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8723) Agent Functions - Create Vault deferred evaluation
Title: Message Title Jayant Sane commented on PUP-8723 Re: Agent Functions - Create Vault deferred evaluation Indeed and I already have tested Vault configured to use PuppetCA and its issued certificates. And yes setting up appropriate authorizations in Vault would need to be done separately (am guessing outside of Puppet or maybe whoever could write a module etc. to automate it via Puppet). Coming to the question of provisioning the individual nodes (agents) with necessary credentials (if/when using anything other than Puppet certificates) to be able to authenticate to Vault, I am wondering if it should be left as an exercise to the user. I was just concerned since there are & could be multitude of ways/options and whatever we try to provide is not likely to satisfy a good portion of users/customers. Creating an intermediary potentially having access to all secrets seems to go against the paradigm/model that users/customers try to go for secret management solutions like Vault (else why not just use hiera/e-yaml). But that was just my personal opinion. All said, I don't have any strong feelings against we providing/implementing either a mechanism to provision some other form of vault credentials on agents or hosting a rest endpoint on puppetserver to get tokens etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-564) I want to know how often each plan function is run
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-564 I want to know how often each plan function is run Change By: Alex Dreyer Fix Version/s: BOLT Next Fix Version/s: BOLT 0.20.7 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-562) I want to know how many targets are present in my inventory file
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Change By: Alex Dreyer Fix Version/s: BOLT Next Fix Version/s: BOLT 0.20.7 Fix Version/s: BOLT 0.20.7 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-491) I want to know how many targets are present in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-491 I want to know how many targets are present in bolt Change By: Alex Dreyer Fix Version/s: BOLT Next Fix Version/s: BOLT 0.20.7 Fix Version/s: BOLT 0.20.7 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-533) Move facts to an external module
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Alex Dreyer Fix Version/s: BOLT Next Fix Version/s: BOLT 0.20.7 Fix Version/s: BOLT 0.20.7 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Nick Walker commented on PUP-8946 Re: Return all eyaml encrypted values from hiera as Sensitive Henrik Lindberg this could be optional in puppet 5 and the new default behavior in 6 yes? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Henrik Lindberg - can you elaborate on using a regex for the key in lookup_options? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Henrik Lindberg commented on PUP-8946 Re: Return all eyaml encrypted values from hiera as Sensitive This probably requires an orchestrated effort with changes to both the function and the eyaml gem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8946 Return all eyaml encrypted values from hiera as Sensitive Change By: Henrik Lindberg Sub-team: Language Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Henrik Lindberg commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type I like PUP-8496. Note that, if your sensitive keys have some pattern to them, then you could drastically reduce the amount of data by using a lookup_options with a regexp key. Introducing automatic type conversion is a lot of work, and not something I think we want in general because of the risk of introducing bugs (that we spent a ton of effort making sure we got rid of in puppet - thing string <-> numeric automatic conversions). For Sensitive it is different as it is basically a contract that the receiver of a value promises that it will handle such a value with care (and is required to do so if it wants to deal with the value in clear text). So in principle I am not against auto type conversion for Sensitive. An implementation would need to do something like first try with the given values, then take each possible function signature and see if it is a Sensitive, and convert values for such parameters, then try that signature, then do the same for the next. This naturally takes performance, but if done as an exception (when nothing else matched) it would only affect auto conversion. For this reason, I like PUP-8496 better. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (PUP-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Henrik Lindberg commented on PUP-8946 Re: Return all eyaml encrypted values from hiera as Sensitive This is a good idea, I think it can be implemented as a parameter to the eyaml_lookup_key function. That would make it backwards compatible, and users that want this can opt in and set an option in their hiera.yaml (by default for all eyaml, or for some paths individually). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Gene Liverman updated an issue Puppet / PUP-8946 Return all eyaml encrypted values from hiera as Sensitive Change By: Gene Liverman Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman updated an issue Puppet / PUP-8947 Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Change By: Gene Liverman Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title
Gene Liverman created an issue
Puppet / PUP-8947
Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/06/15 6:29 AM
Priority:
Normal
Reporter:
Gene Liverman
It seems that when doing a hiera lookup for a class parameter that is of type Sensitive that the string being returned should automatically be cast to Sensitive. The use case here is that I store sensitive data in hiera encrypted in eyaml. I have corresponding profiles that have class parameters defined like so:
class profile::some_profile (
Sensitive[String[1]] $some_sensitive_value,
) {
# puppet code here
}
It is currently a significant amount of extra work to mark each hiera
Jira (PUP-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Gene Liverman created an issue Puppet / PUP-8946 Return all eyaml encrypted values from hiera as Sensitive Issue Type: Improvement Assignee: Unassigned Created: 2018/06/15 6:27 AM Priority: Normal Reporter: Gene Liverman It seems to me that it would be logical to assume that if a value is encrypted via eyaml in hiera that it is sensitive. Based on this, I think all such values should be returned wrapped in the Sensitive type. The result would be that if a String is looked up that a Sensitive[String] would be returned. The same kind of wrapping would hold true for Array, Hash, and Integer too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6521) Add the ability to describe Data Type for a Resource Param
Title: Message Title Henrik Lindberg commented on PUP-6521 Re: Add the ability to describe Data Type for a Resource Param The new Resource API is already doing this to a degree - the data type of parameters/properties can be described by types in the type system. An author uses String, Enum, etc. and can add data types of their own if they need that - from what I have seen, those types can be defined in the resource data type itself (the type definitions are declarative, and only if something is really special would they have to have a backing implementation of the data type). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
