Puppet Community

I just spun up a puppet5, and boy… it already had the deprecation warnings for `puppet ca`, but it definitely works

```USAGE: puppet ca &lt;action&gt;
This provides local management of the Puppet Certificate Authority.```


```[vagrant@master ~]$ puppetserver ca help
Unknown action: help
Usage: puppetserver ca &lt;action&gt; [options]

Manage the Private Key Infrastructure for
Puppet Server's built-in Certificate Authority```

so… “yes” `puppet ca` works there but is already marked as deprecated, and the `puppetserver ca` command should be working <@U04HQ040RD2>

I understand, thank you very much <@U11JXDFJ9>

but FYI, puppet6 is EOL next month, I think

Is there a way to set `$servername` for `puppet apply` ?

what would it be set to ? :slightly_smiling_face:

By definition, `puppet apply`'s server would be the same as `$facts['networking']['fqdn']`.

```$ puppet apply -e 'notice($servername)'
Warning: Unknown variable: 'servername'. (line: 1, column: 8)
Notice: Scope(Class[main]): ```

To be honest, I'm a little surprised `$servername` isn't set when doing puppet apply.

But I guess where ever you're using `$servername`, you would need to check to see if it's defined first, and fall back to the fqdn fact if it's not.

I was doing something like this in the past

Yeah. I'm trying to use a class that is depending on it in a bootstrapping situation. I guess servername is the the server providing the catalog, though.

```$ puppet apply -e 'notice($server_facts)'
Notice: Scope(Class[main]): {environment =&gt; production}

$ puppet apply -e 'notice($servername)'
Warning: Unknown variable: 'servername'. (line: 1, column: 8)```
TIL... I definitely would have assumed server-supplied variables get injected by puppet apply.

I wonder if I can copy the module from `code/environments/production/modules` into `code/modules` and override it there.

Depends on your `modulepath`: <https://www.puppet.com/docs/puppet/7/dirs_modulepath.html#dirs_modulepath-absent-duplicate-conflicting-modules>

Heh. If you do `puppet config set modulepath &lt;new path&gt;`, it puts it into the `[main]` section of `puppet.conf`, and then when you run puppet, it complains that you aren't supposed to set it in `puppet.conf`

When setting modulepath, either do it permanently via `environment.conf`, or one-off via the `--modulepath` CLI option

I guess the basemodulepath probably will achieve what I want, though.