Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Josh Cooper Epic Link: PUP-523 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.24845.1390980091000.84768.1591856940030%40Atlassian.JIRA.
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: Customers see a giant list of classes in the console out of the box. One member of triage described this as installing PE, logging into the console and being in a "room full of red buttons they shouldn't touch". It would be nice if we would either hide the buttons of put some covers on them or something. CS Severity: 2 - Annoyance CS Business Value: 3 - CS Frequency: 5 - >90% of Customers Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Owen Rodabaugh CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Lindsey Smith Team: Puppet Developer Experience 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Thomas Speigner commented on PUP-1534 Re: Puppet classes should be able to declare that they are internal +1 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Moses Mendoza Labels: triaged 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title John Duarte updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: John Duarte Labels: triaged 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title
Henrik Lindberg commented on PUP-1534
Re: Puppet classes should be able to declare that they are internal
We may also want to support private parameters and variables. That is something like this:
class foo::bar(private $a, $b) {
private $x = 'sesame'
$y = 'say friend and enter'
}
This would make an instance of foo::bar visible outside foo, but $foo::bar::a and $foo::bar::x are not, while $foo::bar::b and $foo::bar::y would be.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Henrik Lindberg commented on PUP-1534 Re: Puppet classes should be able to declare that they are internal In order to support this we need to: Update grammar and AST to wire the reserved keyword into the language and resulting AST We can do this element by element (classes, defines, functions, types) Update the loaders to allow elements to only be seen by the creating module - i.e. forbid creation/call Update the runtime so that scope knows if it is a private scope or not (we need to error on cross module variable access) It may be enough to only make creation / call, override, collection and variable access operations private - once a resource is created it may be publically available for functions like defined as well as reading its parameters. This is made somewhat difficult because there is the need to be able to deal with the resource in the catalog, noticing it, etc. which will reveal its values. Further discussion is needed for 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
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title
Henrik Lindberg commented on PUP-1534
Re: Puppet classes should be able to declare that they are internal
I think we may already have a ticket for this (need to look). We have the "private" keyword already in the puppet language, and the idea is to use it as follows:
private class foo() { }
private define foo() { }
private function foo() { }
private type T = T2
The semantics of private is that it may only be created and referenced from the module that contains the definition. In order to make that enforceable we also need to forbid arbitrary namespaces to be used - since as things are now, any manifest can define something in any namespace.
The addition of making the "private" keyword active can be made in a minor release, but the enforcement of namespaces is not backwards compatible and have to wait until a major release.
Add Comment
This message was sent by
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Moses Mendoza Team: Puppet Developer Support 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Moses Mendoza commented on PUP-1534 Re: Puppet classes should be able to declare that they are internal Henrik Lindberg added this one to the PDS backlog 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Luke Kanies created an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Issue Type: Story Assignee: Eric Sorenson Created: 28/Jan/14 11:21 PM Priority: Normal Reporter: Luke Kanies Many classes in Puppet are not meant to be declared directly by a node, and are instead meant only to be used internally. In these cases, the Puppet developer should be able to state that a class is internal, thus preventing that class from showing up in class lists, e.g., in the Console or the API. The primary user benefit of this is that it makes it easy for users configuring classes to focus on the list of classes you might directly associate with a host, rather than having all classes visible, whether they're for external use or not. Add Comment This message was sent by Atlassian JIRA
