Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Kate Lopresti Labels: docs-reviewed 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-632) Scope for bolt_compile should be set up
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Cas Donoghue 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 (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Cas Donoghue Fix Version/s: BOLT Next 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-632) Scope for bolt_compile should be set up
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Michael Smith Assignee: Michael Smith 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-632) Scope for bolt_compile should be set up
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Michael Smith Assignee: Michael Smith 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-632) Scope for bolt_compile should be set up
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Lucy Wyman The scope for manifest block compilation should be properly initialized with:From highest to lowest precedence:- facts hash (reserved, so will error if anything attempts to override it)- vars from the plan scope(excluding ephemeral variables like regex matches)- vars from the target- facts from the target$environment should be set if it is present in the plan scope or the target scope otherwise it should be unset.trusted facts should be set so that:- use host section of target for certname/hostname/domain- set authenticated: localObjects in the plan scope should be serialized and deserialized with pcore.The following values should not be set:Do not set $servername or other master variables.(maybe settings later)Do not set $server_facts(maybe version is useful? but wait for feature requests )Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban 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-632) Scope for bolt_compile should be set up
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Lucy Wyman The scope for manifest block compilation should be properly initialized with:From highest to lowest precedence:- facts hash (reserved, so will error if anything attempts to override it)- vars from the plan scope(excluding ephemeral variables like regex matches)- vars from the target- facts from the target$environment should be set if it is present in the plan scope or the target scope otherwise it should be unset.trusted facts should be set so that:- - use host section of target for certname/hostname/domain- - set authenticated: localObjects in the plan scope should be serialized and deserialized with pcore.The following values should not be set:Do not set $servername or other master variables.(maybe settings later)Do not set $server_facts(maybe version is useful? but wait for feature requests )Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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-632) Scope for bolt_compile should be set up
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Alex Dreyer The scope for manifest block compilation should be properly initialized with:From highest to lowest precedence:- facts hash (reserved, so will error if anything attempts to override it)- vars from the plan scope(excluding ephemeral variables like regex matches)- vars from the target- facts from the target$environment should be set if it is present in the plan scope or the target scope otherwise it should be unset.trusted facts should be set so that:- - use host section of target for certname/hostname/domain- - set authenticated: local Objects in the plan scope should be serialized and deserialized with pcore. The following values should not be set:Do not set $servername or other master variables.(maybe settings later)Do not set $server_facts(maybe version is useful? but wait for feature requests )Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:33 PM Priority: Normal Reporter: Alex Dreyer The scope for manifest block compilation should be properly initialized with: From highest to lowest precedence: facts hash (reserved, so will error if anything attempts to override it) vars from the plan scope(excluding ephemeral variables like regex matches) vars from the target facts from the target $environment should be set if it is present in the plan scope or the target scope otherwise it should be unset. trusted facts should be set so that: - use host section of target for certname/hostname/domain - set authenticated: local The following values should not be set: Do not set $servername or other master variables.(maybe settings later) Do not set $server_facts(maybe version is useful? but wait for feature requests ) Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow.
