Jira (FACT-2438) Remove methods from facter 4 api which are private in facter 3

20 views
Skip to first unread message

Andrei Filipovici (Jira)

unread,
May 28, 2020, 6:13:03 AM5/28/20
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
 
Facter / Improvement FACT-2438
Remove methods from facter 4 api which are private in facter 3
Change By: Andrei Filipovici
Summary: Remove unnecessary Execution module methods from Resolution facter 4 api which are private in facter 3
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Andrei Filipovici (Jira)

unread,
May 28, 2020, 6:17:03 AM5/28/20
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.

weight on resolution is private in facter 3

Andrei Filipovici (Jira)

unread,
May 28, 2020, 7:49:02 AM5/28/20
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.

flush, weight on resolution is are private in facter 3

Andrei Filipovici (Jira)

unread,
May 28, 2020, 7:55:03 AM5/28/20
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.

value, name, execute, flush, weight on resolution are private in facter 3

Mihai Buzgau (Jira)

unread,
Aug 11, 2020, 8:24:04 AM8/11/20
to puppe...@googlegroups.com

Bogdan Irimie (Jira)

unread,
Sep 16, 2020, 9:45:04 AM9/16/20
to puppe...@googlegroups.com
Bogdan Irimie commented on Improvement FACT-2438
 
Re: Remove methods from facter 4 api which are private in facter 3

We should check if it makes sense to make the methods private.

Bogdan Irimie (Jira)

unread,
Sep 16, 2020, 9:48:03 AM9/16/20
to puppe...@googlegroups.com

Bogdan Irimie (Jira)

unread,
Sep 16, 2020, 9:49:03 AM9/16/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ready for triage ghost-23.09

Bogdan Irimie (Jira)

unread,
Sep 23, 2020, 9:11:04 AM9/23/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-23.09 , ready for triage 2

Andrei Filipovici (Jira)

unread,
Sep 28, 2020, 5:46:04 AM9/28/20
to puppe...@googlegroups.com

Andrei Filipovici (Jira)

unread,
Sep 29, 2020, 2:18:03 AM9/29/20
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
The Exception Execution module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.

value, name, execute, flush, weight on resolution are private in facter 3

Bogdan Irimie (Jira)

unread,
Sep 30, 2020, 9:04:05 AM9/30/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-23.09, ghost-30.09 , ready for triage 2

Andrei Filipovici (Jira)

unread,
Oct 2, 2020, 8:37:04 AM10/2/20
to puppe...@googlegroups.com
Andrei Filipovici commented on Improvement FACT-2438
 
Re: Remove methods from facter 4 api which are private in facter 3

Trying to hide some of the Execution module functions, break the LegacyFacter::Util::Config unit tests, because they use the with_env function.
The same thing is valid for the Fact, Resolution and Aggregate classes.
If we use access proxies we need to make sure that methods like define_resolution return the proxy.
All of this makes the code harder to understand and there's little advantage added.

Reply all
Reply to author
Forward
0 new messages