Reading Environment which is no Variables in Puppet

Senin, 10 September 2018

Reading Environment which is no Variables in Puppet

Reading Environment which is no Variables in Puppet - The main problem with phone is that processor. Motorola calls it a ‘blazing-fast 1.4GHz octa-core’ but this isn’t remotely true. It’s an oxymoron: the latest chips run around 1GHz faster than this. Clock speed isn’t the best indicator of performance, but our benchmarks (not that we needed them) confirmed that the G5s is just as sluggish as its predecessor. for the company following, well we have collected a lot of data from the field directly and from many other blogs so very complete his discussion here about Reading Environment which is no Variables in Puppet, on this blog we also have to provide the latest automotive information from all the brands associated with the automobile. ok please continue reading:

Puppet uses a tool called Facter to discover facts about the system it is going to provision. Some examples of these facts are: $operatingsystem, $hostname, $processorcount, etc. These facts are available as variables in puppet to use in manifests. You can see the full list here: Factor 2.0 Core Facts.

If you want an environment variable, or a bash script parameter to be available to puppet, you need to make it available as a Facter fact. You can do that by simply setting a variable whose name is prefixed with the "FACTER_" string.

So for instance, if you wanted to make a variable called say $my_module_name available within puppet, and wanted its value to be equal to environment variable PRODUCT_MODULE_NAME, you could do the following in a bash script that invokes puppet:

export FACTER_my_module_name=$PRODUCT_MODULE_NAME

Now, $my_module_name variable will be available within your puppet manifests.

Setting a Default if Environment Variable is not set

$module_name = $my_module_name ? {
undef => "Admin_Module",
default => $my_module_name
}

Note that the above code uses a different variable name called "module_name", whose value will be set to "Admin_Module" if $my_module_name is un-defined, else it will be set to value of "my_module_name" variable.
Now you can use $module_name in all your puppet manifests (instead of using $my_module_name).

To see a sample code where I did this in Bahmni Hospital Management System provisioning scripts, check out this Github commit: Example.

Tip: If you wish to debug what facts are being set in your system, you can use this snippet to print all facts to a file: Printing all puppet facts.

Tip: If your puppet script is running with "sudo", then the environment variables set in current environment won't be passed to the sudo environment. If you want that, then use "-E" switch with sudo to pass environment variables forward.

for the company following

Senin, 10 September 2018

Reading Environment which is no Variables in Puppet

Setting a Default if Environment Variable is not set

Tidak ada komentar:

Posting Komentar