Jira (PUP-8080) Puppet i18n with Modules: Add basic modules tests
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8080 Puppet i18n with Modules: Add basic modules tests Change By: Eric Delaney Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8080) Puppet i18n with Modules: Add basic modules tests
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8080 Puppet i18n with Modules: Add basic modules tests Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8079) Puppet i18n with Modules: Expanded use-cases and performance
Title: Message Title Michael Smith updated an issue Puppet / PUP-8079 Puppet i18n with Modules: Expanded use-cases and performance Change By: Michael Smith Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8080) Puppet i18n with Modules: Add basic modules tests
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8080 Puppet i18n with Modules: Add basic modules tests Change By: Eric Delaney Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8024) Only load module translations when necessary
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8024
Only load module translations when necessary
Change By:
Maggie Dreyer
Currently, we attempt to initialize translations machinery for all modules as soon as they are loaded, despite the fact in many contexts we do not need to display any translations (e.g. {{module list}}). We do this even for modules that do not have any translation files or marked strings.We also attempt to cache translations after they're loaded, but not associated with any existing cache lifetimes. So the only way to cause a translation to be reloaded is to restart the process.We should add a function to {{module.rb}} that loads a module's translations, then call it before we think we need module translations to be displayed (e.g. before compilation, or when running a puppet application). We should not load translations for things like file serving, in order to avoid doing unnecessary work. We should see if these optimizations are sufficient to reduce the performance impact before doing anything more drastic.*Notes on decoupling module naming from locales/config.yaml project name*From comment below:{quote}As part of this, we should remove the requirement that the module have metadata (relies on forge_name) and remove the coupling of metadata naming and locales/config.yaml's project_name.{quote}Benchmarks in puppet have shown a non-trivial performance degradation if there is a mismatch between the module's metadata name, and the locales/config.yaml's project_name:With matching names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2426-1l58rtz user system totalrealRun 13.70 0.46 4.17 ( 4.171436)Run 22.84 0.13 2.97 ( 2.974983)Run 32.89 0.12 3.01 ( 3.016188)Run 42.91 0.13 3.04 ( 3.036231)Run 52.77 0.15 2.92 ( 2.932649)Run 62.80 0.12 2.92 ( 2.910116)Run 73.24 0.11 3.35 ( 3.359197)Run 82.76 0.15 2.91 ( 2.909707)Run 93.26 0.15 3.41 ( 3.414169)Run 10 3.69 0.14 3.83 ( 3.835340)> total:30.86 1.66 32.53 ( 32.560017)> avg: 3.086000 0.166000 3.253000 ( 3.256002){code}with mismatched names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2350-11p565v user system totalrealRun 13.68 0.46 4.15 ( 4.157170)Run 23.30 0.25 3.55 ( 3.552481)Run 33.18 0.25 3.43 ( 3.430290)Run 43.40 0.26 3.66 ( 3.662123)Run 53.69 0.31 4.00 ( 4.010465)Run 63.60 0.26 3.86 ( 3.866366)Run 73.32 0.25 3.57 ( 3.571592)Run 83.61 0.32 3.93 ( 3.943484)Run 93.56 0.31 3.87 ( 3.866563)Run 10 3.99 0.26 4.25 ( 4.247610)> total:35.33 2.93 38.27 ( 38.308143)> avg: 3.533000 0.293000 3.827000 ( 3.830814){code}Note ~ 6 second cumulative runtime increase Note that a further implication
Jira (PUP-8013) Translations should be stored in different text domains based on environment
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8013
Translations should be stored in different text domains based on environment
Change By:
Maggie Dreyer
if you Users can have config different sets and different versions of modules per Puppet environment . yaml but no In the current system we only load module translations once , and then so if a newer user changes their environment to one with a new version of the module adds translations in it , you may the translations will not use them be updated . If you have the old and We should make translations environment-aware by creating a new versions of text domain for each environment. When we load a module's translations, they should be added to the modules in different environments appropriate text domain , whether translations are and that domain should be loaded will depend on which when the environment is used in changes. Modules should be responsible for loading their own translation files, by adding the translations to a request first gettext repository and adding that repository to the correct text domain . This should be idempotent. We can potentially address need to decide where to initialize the text domains themselves. On the server side, this particular case probably happens as part of the HTTP handler for compilation. On the agent side, this is part of application startup. On the agent side, we don't need to tie text domains to environments because we only ever have one active at once.Text domains should be tied to the environment pollution by associating each gettext "repository" with lifecycle; i.e. when an environment is refreshed, the text domains should be too, to pick up any updates to module translations that occurred. The {{EnvironmentLoader}} might be a good place to put the logic to blow away outdated text domains.[~henrik.lindberg] probably has the most expertise on the environment it was lifecycle and how things are loaded from within an environment .
Add Comment
Jira (PUP-8024) Only load module translations when necessary
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8024
Only load module translations when necessary
Change By:
Maggie Dreyer
Currently, we attempt to initialize translations machinery for all modules as soon as they are loaded, despite the fact in many contexts we do not need to display any translations (e.g. {{module list}}). We do this even for modules that do not have any translation files or marked strings.We also attempt to cache translations after they're loaded, but not associated with any existing cache lifetimes. So the only way to cause a translation to be reloaded is to restart the process.We should add a function to {{module.rb}} that loads a module's translations, then call it before we think we need module translations to be displayed (e.g. before compilation, or when running a puppet application). We should not load translations for things like file serving, in order to avoid doing unnecessary work. We should see if these optimizations are sufficient to reduce the performance impact before doing anything more drastic. *Notes on decoupling module naming from locales/config.yaml project name*From comment below:{quote}As part of this, we should remove the requirement that the module have metadata (relies on forge_name) and remove the coupling of metadata naming and locales/config.yaml's project_name.{quote}Benchmarks in puppet have shown a non-trivial performance degradation if there is a mismatch between the module's metadata name, and the locales/config.yaml's project_name:With matching names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2426-1l58rtz user system totalrealRun 13.70 0.46 4.17 ( 4.171436)Run 22.84 0.13 2.97 ( 2.974983)Run 32.89 0.12 3.01 ( 3.016188)Run 42.91 0.13 3.04 ( 3.036231)Run 52.77 0.15 2.92 ( 2.932649)Run 62.80 0.12 2.92 ( 2.910116)Run 73.24 0.11 3.35 ( 3.359197)Run 82.76 0.15 2.91 ( 2.909707)Run 93.26 0.15 3.41 ( 3.414169)Run 10 3.69 0.14 3.83 ( 3.835340)> total:30.86 1.66 32.53 ( 32.560017)> avg: 3.086000 0.166000 3.253000 ( 3.256002){code}with mismatched names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2350-11p565v user system totalrealRun 13.68 0.46 4.15 ( 4.157170)Run 23.30 0.25 3.55 ( 3.552481)Run 33.18 0.25 3.43 ( 3.430290)Run 43.40 0.26 3.66 ( 3.662123)Run 53.69 0.31 4.00 ( 4.010465)Run 63.60 0.26 3.86 ( 3.866366)Run 73.32 0.25 3.57 ( 3.571592)Run 83.61 0.32 3.93 ( 3.943484)Run 93.56 0.31 3.87 ( 3.866563)Run 10 3.99 0.26 4.25 ( 4.247610)> total:35.33 2.93 38.27 ( 38.308143)> avg: 3.533000 0.293000 3.827000 ( 3.830814){code}Note ~ 6 second cumulative runtime increase Note that a further
Jira (PUP-8024) Delay loading module translations until 'translate' is used for that module
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8024
Delay loading module translations until 'translate' is used for that module
Change By:
Maggie Dreyer
Currently, we attempt to initialize translations machinery for all modules as soon as they are loaded, despite the fact in many contexts we do not need to display any translations (e.g. {{module list}}). We do this even for modules that do not have any translation files or marked strings.We also attempt to cache translations after they're loaded, but not associated with any existing cache lifetimes. So the only way to cause a translation to be reloaded is to restart the process. Instead, we We should look into only initializing gettext for modules when we first need add a function to call the {{ translate() module.rb }} or {{_()}} functions in that loads a module code. This would spread out expensive initialization and avoid 's translations, then call it altogether in contexts where it is unnecessary before we think we need module translations to be displayed (e . g. before compilation, or when running a puppet application). *Notes on decoupling module naming from locales/config.yaml project name*From comment below:{quote}As part of this, we should remove the requirement that the module have metadata (relies on forge_name) and remove the coupling of metadata naming and locales/config.yaml's project_name.{quote}Benchmarks in puppet have shown a non-trivial performance degradation if there is a mismatch between the module's metadata name, and the locales/config.yaml's project_name:With matching names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2426-1l58rtz user system totalrealRun 13.70 0.46 4.17 ( 4.171436)Run 22.84 0.13 2.97 ( 2.974983)Run 32.89 0.12 3.01 ( 3.016188)Run 42.91 0.13 3.04 ( 3.036231)Run 52.77 0.15 2.92 ( 2.932649)Run 62.80 0.12 2.92 ( 2.910116)Run 73.24 0.11 3.35 ( 3.359197)Run 82.76 0.15 2.91 ( 2.909707)Run 93.26 0.15 3.41 ( 3.414169)Run 10 3.69 0.14 3.83 ( 3.835340)> total:30.86 1.66 32.53 ( 32.560017)> avg: 3.086000 0.166000 3.253000 ( 3.256002){code}with mismatched names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2350-11p565v user system totalrealRun 13.68 0.46 4.15 ( 4.157170)Run 23.30 0.25 3.55 ( 3.552481)Run 33.18 0.25 3.43 ( 3.430290)Run 43.40 0.26 3.66 ( 3.662123)Run 53.69 0.31 4.00 ( 4.010465)Run 63.60 0.26 3.86 ( 3.866366)Run 73.32 0.25 3.57 ( 3.571592)Run 83.61 0.32 3.93 ( 3.943484)Run 93.56 0.31 3.87 ( 3.866563)Run 10 3.99 0.26 4.25 ( 4.247610)> total:35.33 2.93 38.27 ( 38.308143)> avg: 3.533000 0.293000 3.827000 ( 3.830814){code}Note ~ 6 second
Jira (PUP-8024) Only load module translations when necessary
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8024 Only load module translations when necessary Change By: Maggie Dreyer Summary: Delay loading Only load module translations until 'translate' is used for that module when necessary Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8013) Translations should be stored in different text domains based on environment
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8013 Translations should be stored in different text domains based on environment Change By: Maggie Dreyer Summary: Modules with translations may Translations should be shadowed by older versions of those modules stored in different text domains based on environment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8026) Module code translation should be supported with puppet agent runs
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8026
Module code translation should be supported with puppet agent runs
Change By:
Maggie Dreyer
Translation support in Puppet was extended to Puppet code in modules. It also appears to be expected to support any Ruby code in modules, such as custom facts, types and providers, and Puppet functions.This works with {{puppet apply}}. However, we don't appear to do anything to pluginsync the locales directory containing those translations to agents to make them available during a {{puppet agent}} run. We should. In order to get pluginsync working, we need a locale mountpoint on the server with the locale files, each of which has a unique name based on the module name. These come from the {{locales}} subdirectories of modules. We only want to sync the PO files, not the config files. We either need to preserve the directory structure or only download the one locale we need (or both). We should probably start by downloading all locales to keep things simple.Adding the downloader on the agent side should be a relatively simple addition, thanks to metaprogramming. We should have these translations be kept separate from the main plugin directory. See {{configurer/downloader_factory.rb}}.Once we have the translation files, we should load them into the text domain for the current environment at the start of every Puppet application call. This can likely be added to the application base. The first time that this happens on the agent, there won't be any translations. We need to load translations every time we pluginsync and re-evaluate facts, to make sure that we really have loaded the ones for the correct environment, so this should probably be added to the pluginsync functionality.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8081) Create tests for expanded module I18N testing
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8081 Create tests for expanded module I18N testing Change By: Eric Delaney Need to create tests for the following I18n and modules cases:* Module in multiple environments* Run puppet agent multiple times without restarting the server* Puppet Functions, custom facts, manifests, types, providers* puppet agent, apply, facts, describe, resource* Can still disable translations globally* Verify fall back when language not available* server side non-EN locale< /span> Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8081) Create tests for expanded module I18N testing
Title: Message Title Eric Delaney created an issue Puppet / PUP-8081 Create tests for expanded module I18N testing Issue Type: Task Assignee: Unassigned Created: 2017/10/20 3:32 PM Priority: Normal Reporter: Eric Delaney Need to create tests for the following I18n and modules cases: Module in multiple environments Run puppet agent multiple times without restarting the server Puppet Functions, custom facts, manifests, types, providers puppet agent, apply, facts, describe, resource Can still disable translations globally server side non-EN locale
Jira (PUP-8080) Puppet i18n with Modules: Add basic modules tests
Title: Message Title Eric Delaney created an issue Puppet / PUP-8080 Puppet i18n with Modules: Add basic modules tests Issue Type: Task Assignee: Unassigned Created: 2017/10/20 3:27 PM Priority: Normal Reporter: Eric Delaney Add tests for the following cases: Need a module with a non puppet locale Modules with locale's not in Puppet Multiple requests against puppetserver Need to understand what is required to produce the failure Add Comment
Jira (PUP-6824) Use UUIDs for certificate serial numbers
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6824 Use UUIDs for certificate serial numbers Change By: Owen Rodabaugh CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8079) Puppet i18n with Modules: Expanded use-cases and performance
Title: Message Title Larissa Lane updated an issue Puppet / PUP-8079 Puppet i18n with Modules: Expanded use-cases and performance Change By: Larissa Lane Labels: i18n Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3728) 404 puppetdb Low catalog duplication page
Title: Message Title Wyatt Alt commented on PDB-3728 Re: 404 puppetdb Low catalog duplication page the issue this page used to address hasn't been a concern since probably 2.3.x. I think any current references to it are safe to remove. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3729) Invalid JSON example for puppetdb.conf
Title: Message Title Michelle Fredette moved an issue PuppetDB / PDB-3729 Invalid JSON example for puppetdb.conf Change By: Michelle Fredette Method Found: Needs Assessment Component/s: Puppet Client/Agent Workflow: Documentation Scrum Team Workflow Key: DOCUMENT PDB - 678 3729 Project: Documentation PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PDB-3728) 404 puppetdb Low catalog duplication page
Title: Message Title Michelle Fredette moved an issue PuppetDB / PDB-3728 404 puppetdb Low catalog duplication page Change By: Michelle Fredette Method Found: Needs Assessment Component/s: PuppetDB Component/s: PuppetDB Workflow: Documentation Scrum Team Workflow Key: DOCUMENT PDB - 679 3728 Project: Documentation PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Jean Bond updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Jean Bond updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Jean Bond Release Notes Summary: The Error object did not support being initialized from a hash with arguments for the error object. It was only possible to give it the error message as a string. docs note: Documented in Bolt 0.6, will need a Puppet 5.4 release note. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7975) "LANG=ja_JP puppet enterprise support" produces non-printable error
Title: Message Title Brandon High commented on PUP-7975 Re: "LANG=ja_JP puppet enterprise support" produces non-printable error Charlie Sharpsteen Any ideas what would be causing this? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Jayant Sane assigned an issue to Jayant Sane Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems Change By: Jayant Sane Assignee: Jayant Sane Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8079) Puppet i18n with Modules: Expanded use-cases and performance
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8079 Puppet i18n with Modules: Expanded use-cases and performance Change By: Maggie Dreyer Epic Name: Puppet i18n with Modules : Expanded use-cases and performance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8079) Puppet i18n with Modules: Expanded use-cases and performance
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8079 Puppet i18n with Modules: Expanded use-cases and performance Change By: Maggie Dreyer Summary: Puppet i18n with Modules : Expanded use-cases and performance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8079) Puppet i18n with Modules
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8079 Puppet i18n with Modules Issue Type: Epic Assignee: Unassigned Created: 2017/10/20 11:08 AM Priority: Normal Reporter: Maggie Dreyer This epic contains the work needed to get modules translations fully functional in all configurations, while maintaining good performance. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6824) Use UUIDs for certificate serial numbers
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-6824 Use UUIDs for certificate serial numbers Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7987) Add support to defined top scope variables to the Pal API
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-7987 Add support to defined top scope variables to the Pal API Change By: Eric Sorenson Fix Version/s: BOLT 0.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7974) puppet master compile command with language in japanese doesn't print solution in japanese
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7974 puppet master compile command with language in japanese doesn't print solution in japanese Change By: Eric Thompson Labels: exploratory_testing Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7975) "LANG=ja_JP puppet enterprise support" produces non-printable error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7975 "LANG=ja_JP puppet enterprise support" produces non-printable error Change By: Eric Thompson Labels: exploratory_testing Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7781 yumrepo don't support payload_gpgcheck option Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7745 package latest method does not refresh metadata on Solaris Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Eric Delaney updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Eric Delaney QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3713) Allow zfs to create a zvol
Title: Message Title Eric Delaney updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Eric Delaney QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6452) Allow defaultfor to accept regex
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Eric Delaney QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7292) Allow to set password warning days for user type
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7672) The ZFS zoned property is not portable
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7672 The ZFS zoned property is not portable Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7807) AIX mount resource remounts without options
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7807 AIX mount resource remounts without options Change By: Eric Delaney QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8045) Add support for Fedora 26 in the dnf provider
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8045 Add support for Fedora 26 in the dnf provider Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Henrik Lindberg Assignee: Thomas Hallgren Release Notes Summary: It is no longer required to have a dependency listed in a module's metadata.json on another module (b) in order to use functions or data types from module b. Sprint: Tasks Kanban Release Notes: New Feature Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8072) Merge tasks/scripts feature branch to puppet master
Title: Message Title Henrik Lindberg commented on PUP-8072 Re: Merge tasks/scripts feature branch to puppet master When doing this, we must do PUP-6964 (PR up for that now) since the requirement that a module must have dependencies on other modules makes it impossible for bolt to provide functions that are visible to other modules unless they declare their dependency on this bolt supplied module. This would trip up almost everyone. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-588) Removing calling_module breaks perfectly valid usage
Title: Message Title Henrik Lindberg commented on HI-588 Re: Removing calling_module breaks perfectly valid usage As pointed out, this works with v3 global hiera.yaml since the new version is backwards compatible, but not anywhere else. It is important to understand that use of calling_module in practice means that the cache must be evicted per lookup that does not come from the same module as the one before it, and this has a performance impact. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg commented on PUP-8056 Re: Error type docs show new from hash - does not work as intended Jean Bond If we released support for the Error type in 5.3 then this needs a release note for 5.4. I don't think we released the Error type in 5.3.x though. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-588) Removing calling_module breaks perfectly valid usage
Title: Message Title Henrik Lindberg commented on HI-588 Re: Removing calling_module breaks perfectly valid usage The functionality that calling_module provides is strange because it makes values be different depending on from where you are looking them up. This makes them difficult to deal with. There are two primary use cases for calling_module: things in modules - as mentioned in the documentation, and these can be replaced with the new "data in module" keeping separate data files with overrides per module to enable maintenance by different users - this can be replaced with the glob pattern What you cannot achieve with the new version is that a key has different value depending on the context it is looked up from. Do you really need that? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-588) Removing calling_module breaks perfectly valid usage
Title: Message Title Henrik Lindberg assigned an issue to Joerg Jaspert Hiera / HI-588 Removing calling_module breaks perfectly valid usage Change By: Henrik Lindberg Assignee: Joerg Jaspert Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8070) cannot extract partial result from errors in plans
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8070 cannot extract partial result from errors in plans Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7987) Add support to defined top scope variables to the Pal API
Title: Message Title Henrik Lindberg commented on PUP-7987 Re: Add support to defined top scope variables to the Pal API This change is in Puppet, not in Bolt. Needs to have a PUP release version. Ping Eric Sorenson - the feature in this ticket is actually not used in Bolt for anything. (In general we do need to figure out how to tag changes/release-note in PUP that are only relevant to Bolt). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8078) Make it possible to create parameterized Object data types
Title: Message Title Henrik Lindberg commented on PUP-8078 Re: Make it possible to create parameterized Object data types After a discussion (Thomas and I) we updated the proposal to use type_parameters instead of parameters to make it clearer that what is being stated is something for the type being constructed as opposed to something for instances of the type). We also discussed if the support for type parameters should be implemented in a more generic way; some kind of definition that is a more substantial meta description, but we concluded that it would take too much time to specify that in more detail. Instead, sometime in the future if more things are needed at the meta level (the type of the type) we would need to then take the currently proposed type_parameter into account. Given that we have quite a few concepts and feature still to implement at the instance level we are nowhere near working on features at the meta type level. So, type_parameters it is. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8078) Make it possible to create parameterized Object data types
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8078
Make it possible to create parameterized Object data types
Change By:
Henrik Lindberg
It is currently not possible to create an {{Object}} data type that is parameterized. The type itself can thus only be used to filter instances based on their type, not on contents. This is highly desirable in some cases.A first implementation should allow parameterized types to be created with filtering logic implemented in Ruby. Later, we might add predefined filters such as using {{Pattern}}, {{String}}, or {{Enum}} to match string attributes, min/max filters for magnitudes, or {{Boolean}} filters to match if attributes have a value or not.The parameters for an {{Object}} type can be added using a new top level property named {{ parameters type_parameters }}. The value of this property is a hash similar to {{attributes}} where a parameter declaration is a subset of an attribute declaration. The parameter can have a {{type}} and a {{value}} but is different from an attribute in that a parameter is always optional (a required parameter would break the current pattern where a fully generalized type exists for each parameterized type).A parameterized `Object` type, when serialized, must retain the values of its parameters.Example:{code:puppet}type Error = Object[ parameters type_parameters => {kind => Variant[String, Regexp, Type[Enum], Type[Pattern]],issue_code => Variant[String, Regexp, Type[Enum], Type[Pattern]] }, attributes => {message => String[1],kind => { type => Optional[String[1]], value => undef },issue_code => { type => Optional[String[1]], value => 'ERROR' },partial_result => { type => Data, value => undef },details => { type => Optional[Hash[String[1],Data]], value => undef }, }]{code}The above declaration makes it possible to create a parameterized {{Error}} by either providing no parameters at all, one {{Hash}} parameter with named arguments, or one or two anonymous (positional) arguments.
Add Comment
Jira (PUP-8078) Make it possible to create parameterized Object data types
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-8078
Make it possible to create parameterized Object data types
Change By:
Thomas Hallgren
It is currently not possible to create an {{Object}} data type that is parameterized. The type itself can thus only be used to filter instances based on their type, not on contents. This is highly desirable in some cases.A first implementation should allow parameterized types to be created with filtering logic implemented in Ruby. Later, we might add predefined filters such as using {{Pattern}}, {{String}}, or {{Enum}} to match string attributes, min/max filters for magnitudes, or {{Boolean}} filters to match if attributes have a value or not.The parameters for an {{Object}} type can be added using a new top level property named {{parameters}}. The value of this property is a hash similar to {{attributes}} where a parameter declaration is a subset of an attribute declaration. The parameter can have a {{type}} and a {{value}} but is different from an attribute in that a parameter is always optional (a required parameter would break the current pattern where a fully generalized type exists for each parameterized type).A parameterized `Object` type, when serialized, must retain the values of its parameters.Example:{code:puppet}type Error = Object [ parameters => {kind => Variant[String, Regexp, Type[Enum], Type[Pattern]],issue_code => Variant[String, Regexp, Type[Enum], Type[Pattern]] }, attributes => {message => String[1],kind => { type => Optional[String[1]], value => undef },issue_code => { type => Optional[String[1]], value => 'ERROR' },partial_result => { type => Data, value => undef },details => { type => Optional[Hash[String[1],Data]], value => undef }, }]{code}The above declaration makes it possible to create a parameterized {{Error}} by either providing no parameters at all, one {{Hash}} parameter with named arguments, or one or two anonymous (positional) arguments.
Add Comment
This message
Jira (PUP-8078) Make it possible to create parameterized Object data types
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-8078
Make it possible to create parameterized Object data types
Change By:
Thomas Hallgren
It is currently not possible to create an ` {{ Object ` }} data type that is parameterized. The type itself can thus only be used to filter instances based on their type, not on contents. This is highly desirable in some cases.A first implementation should allow parameterized types to be created with filtering logic implemented in Ruby. Later, we might add predefined filters such as using {{Pattern}}, {{String}}, or {{Enum}} to match string attributes, min/max filters for magnitudes, or {{Boolean}} filters to match if attributes have a value or not.The parameters for an {{Object}} type can be added using a new top level property named {{parameters}}. The value of this property is a hash similar to {{attributes}} where a parameter declaration is a subset of an attribute declaration. The parameter can have a {{type}} and a {{value}} but is different from an attribute in that a parameter is always optional (a required parameter would break the current pattern where a fully generalized type exists for each parameterized type).A parameterized `Object` type, when serialized, must retain the values of its parameters.Example:{code:puppet}type Error[ parameters => {kind => Variant[String, Regexp, Type[Enum], Type[Pattern]],issue_code => Variant[String, Regexp, Type[Enum], Type[Pattern]] }, attributes => {message => String[1],kind => { type => Optional[String[1]], value => undef },issue_code => { type => Optional[String[1]], value => 'ERROR' },partial_result => { type => Data, value => undef },details => { type => Optional[Hash[String[1],Data]], value => undef }, }]{code}The above declaration makes it possible to create a parameterized {{Error}} by either providing no parameters at all, one {{Hash}} parameter with named arguments, or one or two anonymous (positional) arguments.
Add Comment
This message was
Jira (PUP-8078) Make it possible to create parameterized Object data types
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8078 Make it possible to create parameterized Object data types Issue Type: Bug Assignee: Unassigned Created: 2017/10/20 2:00 AM Priority: Normal Reporter: Thomas Hallgren It is currently not possible to create an `Object` data type that is parameterized. The type itself can thus only be used to filter instances based on their type, not on contents. This is highly desirable in some cases. A first implementation should allow parameterized types to be created with filtering logic implemented in Ruby. Later, we might add predefined filters such as using Pattern, String, or Enum to match string attributes, min/max filters for magnitudes, or Boolean filters to match if attributes have a value or not. The parameters for an Object type can be added using a new top level property named parameters. The value of this property is a hash similar to attributes where a parameter declaration is a subset of an attribute declaration. The parameter can have a type and a value but is different from an attribute in that a parameter is always optional (a required parameter would break the current pattern where a fully generalized type exists for each parameterized type). A parameterized `Object` type, when serialized, must retain the values of its parameters. Example: type Error[
