Hi Guys,

I'm trying to figure out the best way to manage json configuration files on 
all of my nodes. The json files consist of from 1 to n sub-site 
configurations stored in a json array.  If each site only had 1 site 
configuration, it would be a simple matter of using a template.  The only 
option I can think of right now is to maintain a separate json file for 
each node on the Puppet Master.  Of course, that would make implementing 
across-the-board changes cumbersome.

What are my options?

Each node's json file would look something like this and could have any 
number of sites:

{
  "Sites": [
    {
      "ID": "0000",
      "IS_LIVE": "False",
      "MYSQL_USER": "mgmt",
      "MYSQL_PASS": "letmein",
      "LIVE_DIR": "/srv/www/0000.net",
      "BACKUP_LIVE": "True"
    }

  {
      "ID": "0001",
      "IS_LIVE": "False",
      "MYSQL_USER": "mgmt",
      "MYSQL_PASS": "letmein",
      "LIVE_DIR": "/srv/www/0001.net",
      "BACKUP_LIVE": "True"

    }

  {
      "ID": "0002",
      "IS_LIVE": "False",
      "MYSQL_USER": "mgmt",
      "MYSQL_PASS": "letmein",
      "LIVE_DIR": "/srv/www/0002.net",
      "BACKUP_LIVE": "True"

    } 

]
}

Thanks for any suggestions on the best way to manage these files.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5e14eb66-2a77-4556-a783-96e3d6f1feb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to