Ignored_environments.yml

Support
1

I'm running Foreman 1.5.1 (via foreman installer) alongside puppet 3.4.2 on
Ubuntu 14.04. I am having difficulty getting Foreman to filter out Puppet
classes from import, using the /etc/foreman/ignored_environments.yml file.
At the moment, the contents are the same as the standard sample YML file:

:filters:

  • !ruby/regexp '/install$/'
  • !ruby/regexp '/params$/'
  • !ruby/regexp '/repo$/'

I do have several matching puppet classes installed, and as far as I can
tell none are being excluded from the import: java::params, ntp::install,
postgresql::repo, etc. The ignored_environments.yml file seems to have no
effect on the import.

I'm wondering if this feature is even available in 1.5+; official docs
still mention it (section 4.2.2), but I've seen no other mention of this
since ~ Foreman 1.2 days. Also wondering if I need to explicitly enable
this, in some way other than ensuring the presence of the
ignored_environments.yml file in /etc/foreman?

Thanks in advance for any help you can provide.

2

FYI, I found the cause for this… /etc/foreman is not the real config
directory under Ubuntu. /usr/share/foreman/config contains a symbolic link
back to the foreman.conf file in /etc/foreman. Discovering this wasn't
easy; traditionally the symbolic link would go in the opposite direction,
or the entire config directory would be a link instead.

··· On Monday, July 21, 2014 3:24:04 PM UTC-4, dc131 wrote: > > I'm running Foreman 1.5.1 (via foreman installer) alongside puppet 3.4.2 > on Ubuntu 14.04. I am having difficulty getting Foreman to filter out > Puppet classes from import, using the /etc/foreman/ignored_environments.yml > file. At the moment, the contents are the same as the standard sample YML > file: > > :filters: > - !ruby/regexp '/install$/' > - !ruby/regexp '/params$/' > - !ruby/regexp '/repo$/' > > I do have several matching puppet classes installed, and as far as I can > tell none are being excluded from the import: java::params, ntp::install, > postgresql::repo, etc. The ignored_environments.yml file seems to have no > effect on the import. > > I'm wondering if this feature is even available in 1.5+; official docs > still mention it (section 4.2.2), but I've seen no other mention of this > since ~ Foreman 1.2 days. Also wondering if I need to explicitly enable > this, in some way other than ensuring the presence of the > ignored_environments.yml file in /etc/foreman? > > Thanks in advance for any help you can provide. >