Jira (FACT-1652) Create a feature flag setting for Facter 4 features during Facter 3 lifetime

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1652 Create a feature flag setting for Facter 4 features during Facter 3 lifetime Change By: Branan Riley Sprint: Agent N+1 Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Branan Riley (JIRA)]

Branan Riley created an issue

Facter / FACT-1652 Create a feature flag setting for Facter 4 features during Facter 3 lifetime

Issue Type: New Feature Assignee: Unassigned Created: 2017/06/21 10:17 AM Fix Versions: FACT 3.y Priority: Normal Reporter: Branan Riley We will need a mechanism to ship dark changes during the Facter 3 series that are targeted to go live / on by default in Facter 4 In Scope Create a facter setting that can be used to determine whether a user wants to opt into possible future behavior of puppet (including breaking changes) This should be the same setting used by puppet in PUP-7677 Docs should note that code enabled with the `--future-features` flag is experimental and subject to change, especially based on user feedback

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Facter / FACT-1652 Create a feature flag setting for Facter 4 features during Facter 3 lifetime

Change By: Geoff Nichols Sprint: Agent N+1

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

Facter / FACT-1652 Create a feature flag setting for Facter 4 features during Facter 3 lifetime

Change By: Claudia Petty Labels: new-feature

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)