Jira (FACT-2639) facter.conf location should be dependent on Agent AIO version

[Bogdan Irimie (Jira)]

Bogdan Irimie created an issue

Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Issue Type: Task Assignee: Unassigned Created: 2020/05/28 1:22 AM Priority: Normal Reporter: Bogdan Irimie When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf` When not in AIO context, Facter should read facter.conf from the gem root location. Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Bogdan Irimie (Jira)]

Bogdan Irimie updated an issue

Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version

Change By: Bogdan Irimie

When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf` When not in AIO context, Facter should read facter.conf from the gem root location.

Since `facter.conf` was introduced in Facter 3, the change does not affect clients that migrate from Facter 2 to Facter 4. Client that were using Facter 3, were using the Puppet AIO version, so they will not be impacted affected by this change.   The main advantage of this approach is that we can have different facter.conf files for different gems on Facter (e.g. the Facter from AIO agent can have a facter config, while the one from pe_installer can have another config)

Add Comment

[Bogdan Irimie (Jira)]

Bogdan Irimie updated an issue

Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Change By: Bogdan Irimie

When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf` When not in AIO context, Facter should read facter.conf from the gem root location.

Since `facter.conf` was introduced in Facter 3, the change does not affect clients that migrate from Facter 2 to Facter 4. Client that were using Facter 3, were using the Puppet AIO version, so they will not be impacted by this change.

The main advantage of this approach is that we can have different facter.conf files for different gems on Facter (e.g. the Facter from AIO agent can have a facter config, while the one from pe_installer can have another config)

Add Comment

[Bogdan Irimie (Jira)]

Bogdan Irimie updated an issue

Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Change By: Bogdan Irimie

When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf` When not in AIO context, Facter should read facter.conf from the gem root location.

Since `facter.conf` was introduced in Facter 3, the change does not affect clients that migrate from Facter 2 to Facter 4. Client that were are using Facter 3, were are using the Puppet AIO version, so they will not be affected by this change.

The main advantage of this approach is that we can have different facter.conf files for different gems on Facter (e.g. the Facter from AIO agent can have a facter config, while the one from pe_installer can have another config)

Add Comment