Jira (FACT-1628) Set of breaking changes staged for facter 4

4 views
Skip to first unread message

Sean McDonald (JIRA)

unread,
May 17, 2017, 12:27:04 PM5/17/17
to puppe...@googlegroups.com
Sean McDonald created an issue
 
Facter / Epic FACT-1628
Set of breaking changes staged for facter 4
Issue Type: Epic Epic
Assignee: Unassigned
Created: 2017/05/17 9:26 AM
Labels: triaged
Priority: Normal Normal
Reporter: Sean McDonald
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Michael Smith (JIRA)

unread,
May 18, 2017, 12:36:02 PM5/18/17
to puppe...@googlegroups.com

Moses Mendoza (JIRA)

unread,
May 18, 2017, 1:49:43 PM5/18/17
to puppe...@googlegroups.com

Branan Riley (JIRA)

unread,
May 30, 2017, 9:56:02 AM5/30/17
to puppe...@googlegroups.com
Branan Riley commented on Epic FACT-1628
 
Re: Set of breaking changes staged for facter 4

Not 5. Facter Next will be going out with Puppet/Agent 6, so we should either stick to 4 or rev it all the way to 6. I don't have strong feelings.

Geoff Nichols (JIRA)

unread,
Jul 22, 2017, 1:52:04 AM7/22/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
 
Change By: Geoff Nichols
Team/s: Agent Platform OS

Branan Riley (JIRA)

unread,
Mar 21, 2018, 7:04:04 PM3/21/18
to puppe...@googlegroups.com
Branan Riley updated an issue
Change By: Branan Riley
Labels: triaged
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Branan Riley (JIRA)

unread,
Mar 22, 2018, 6:08:03 PM3/22/18
to puppe...@googlegroups.com
Branan Riley commented on Epic FACT-1628
 
Re: Set of breaking changes staged for facter 4

I've re-populated this with the set of tickets I believe would be good to target here.

Along with FACT-747 for Solaris, we should also look in to using the same method on AIX, the BSDs, and possibly Windows. Additionally, we have a couple tickets around how the default-route-based primary interface detection can fail. It might be nice to come up with a fallback method for when the default route looks like nonsense. One suggested method was using whatever IP the hostname resolves to (as long as its not loopback). I'll need to go through the networking tickets to finish scoping that work.

Branan Riley (JIRA)

unread,
Mar 26, 2018, 12:52:05 PM3/26/18
to puppe...@googlegroups.com
Branan Riley commented on Epic FACT-1628

The more I dig into the networking tickets, the more I'm unsure they can be collected into one or two neat fixes. I'm going to punt on adding anything in that space for now.

Kenn Hussey (JIRA)

unread,
Mar 26, 2018, 3:28:02 PM3/26/18
to puppe...@googlegroups.com
Kenn Hussey updated an issue
 
Change By: Kenn Hussey
Fix Version/s: FACT 4.0.0

Josh Cooper (Jira)

unread,
Feb 3, 2021, 7:58:03 PM2/3/21
to puppe...@googlegroups.com
Josh Cooper commented on Epic FACT-1628
 
Re: Set of breaking changes staged for facter 4

Hi Bogdan Irimie I ran across this epic, unfortunately too late for facter 4. But maybe for next time?

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages