Configuration precedence and puppet code

There are several ways to configure puppet code, but some configuration methods take precedence over others.

If no other configuration is specified, puppet code uses the settings in the global configuration file. User-specific configuration files override the global configuration file.

If you Use a temporary puppet code.conf file, Puppet temporarily uses that configuration file only. In this case, Puppet doesn't read the global or user-specific configuration files at all for that one deployment.

If you Use a temporary cacert, token-file, or service-url, by specifying individual configuration options directly on the command line, those options temporarily take precedence over any place they are specified in default, global, or user-specific configuration file settings. Settings you don't specify in this way are applied according to their normal configuration precedence.