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

1 view
Skip to first unread message

Branan Riley (JIRA)

unread,
Jun 21, 2017, 1:18:03 PM6/21/17
to puppe...@googlegroups.com
Branan Riley updated an issue
 
Facter / New Feature 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 Add Comment
 
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Branan Riley (JIRA)

unread,
Jun 21, 2017, 1:18:03 PM6/21/17
to puppe...@googlegroups.com
Branan Riley created an issue
Issue Type: New Feature New Feature
Assignee: Unassigned
Created: 2017/06/21 10:17 AM
Fix Versions: FACT 3.y
Priority: Normal 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

Geoff Nichols (JIRA)

unread,
Jul 19, 2017, 12:07:03 PM7/19/17
to puppe...@googlegroups.com

Claudia Petty (Jira)

unread,
Jun 21, 2023, 8:44:04 AM6/21/23
to puppe...@googlegroups.com
Claudia Petty updated an issue
Change By: Claudia Petty
Labels: new-feature
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages