cheftacular 2.13.1 → 2.13.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 92f2e70957d1d62c5599891b291c67693b3577de
-  data.tar.gz: c02911fd60f6acb0b49bc9ad3011a22caf57d90c
+  metadata.gz: 1a426853edae71510b1d45b85e5ec0458cc1cb84
+  data.tar.gz: 12482be7a61f011eb367a4da241c34f5897ebc87
 SHA512:
-  metadata.gz: 3153b70f011016ee0f051a9d423eab7042b2501e088e959701cf09600ab78c9a025b82474017b1a2d3505e19c63941fe202d40d0315881666362847edea0212d
-  data.tar.gz: ec88f2eaac833915e014a53fdd665d5748ab5ddb9da1228fce851889f91e8b38b01119af5afabecf79490d314d870096f1bd0d91a0567b412d0e0a17ed874fa1
+  metadata.gz: 5e4a01ad45c27f56ca5a80b34705e1a844c8a9edcc6f83df8bfed791087aa52e93b41acbd00678652e3f3c8e32cbdc73fa2304d5772b01021d5674bed5006cff
+  data.tar.gz: 1a94cb22a4b198c3f16763ca3ca13c6ecd55d33453f5470866f728a8960aa254548f99838c79e2810a23adae1dada6e2de6c7f74a00ab6d145a2657582d78fa6

data/lib/cheftacular/README.md

@@ -82,6 +82,10 @@
 
     5. `restore` will simply just run the _backup loading command_ to load the latest backup onto the server.
 
+    6. `status` will display the current state of the backups
+
+    6. By default, the backups command will use the context of your current environment to trigger backup related commands.
+
 2. `cft check [all]` Checks the commits for all servers for a repository (for an environment) and returns them in a simple chart. Also shows when these commits were deployed to the server.
 
     1. If the node has special repository based keys from TheCheftacularCookbook, this command will also display information about the branch and organization currently deployed to the node(s).
@@ -286,6 +290,8 @@
 
     4. IMPORTANT NOTE: You cannot run `cft run rake -T` as is, you have to enclose any command that uses command line dash arguments in quotes like `cft run "rake -T"`
 
+    5. Can also be used to run meteor commands and is aliased to `cft meteor`
+
 28. `cft scale up|down [NUM_TO_SCALE]` will add (or remove) NUM_TO_SCALE servers from the server array. This command will not let you scale down below 1 server.
 
     1. In the case of server creation, this command takes a great deal of time to execute. It will output what stage it is currently on to the terminal but <b>you must not kill this command while it is executing</b>.A failed build may require the server to be destroyed / examined by a DevOps engineer.
@@ -313,25 +319,13 @@
 
     1. `SPECIFIC_REPOSITORY` is a special argument, if left blank the key will be placed in the authorized_keys array in the bag, otherwise it will be placed in the specific_authorized_keys hash under a key named for the repository that is passed. The script will error if SPECIFIC_REPOSITORY does not exist in the cheftacular.yml respositories hash. You can then use this data to give users selective ssh access to certain servers.
 
-3. `cft backups [activate|deactivate|fetch|load|restore]` this command sets the fetch_backups and restore_backups flags in your config data bag for an environment. These can be used to give application developers a way to trigger / untrigger restores in an environment
-
-    1. `activate` will turn on automated backup running (turns on the flag for the env in the config bag).
-
-    2. `deactivate` will turn off automated backup running.
-
-    3. `fetch` will fetch the latest backup and drop it onto your machine. This argument accepts the --save-to-file LOCATION flag.
-
-    4. `load` will fetch the latest backup from the production primary **if it doesn't already exist on the server** and run the _backup loading command_ to load this backup into the env.
-
-    5. `restore` will simply just run the _backup loading command_ to load the latest backup onto the server.
-
-4. `cft check_cheftacular_yml_keys` allows you to check to see if your cheftacular yml keys are valid to the current version of cheftacular. It will also set your missing keys to their likely default and let you know to update the cheftacular.yml file.
+3. `cft check_cheftacular_yml_keys` allows you to check to see if your cheftacular yml keys are valid to the current version of cheftacular. It will also set your missing keys to their likely default and let you know to update the cheftacular.yml file.
 
-5. `cft chef_bootstrap_from_queue` allows you to register a node in the chef system, remove any lingering data that may be associated with it and update the node's runlist if it has an entry in nodes_dir for its NODE_NAME.
+4. `cft chef_bootstrap_from_queue` allows you to register a node in the chef system, remove any lingering data that may be associated with it and update the node's runlist if it has an entry in nodes_dir for its NODE_NAME.
 
     1. This command is part of the `cft full_bootstrap` command and cannot be called directly
 
-6. `cft chef_server [restart|processes|memory]` this command can be used to query the chef server for stats if the cheftacular.yml has the chef_server key filled out. Useful for low resource chef-servers.
+5. `cft chef_server [restart|processes|memory]` this command can be used to query the chef server for stats if the cheftacular.yml has the chef_server key filled out. Useful for low resource chef-servers.
 
     1. `restart` restarts all chef processes on the chef server which may alleviate slow cheftacular load times for some users. (NOTE) do not run this command while the chef-server is performing actions or instability may result! Not tested for high volume chef servers.
 
@@ -343,7 +337,7 @@
 
     5. NOTE 2! Cheftacular does not (and will not) support accessing your chef server over ssh with password auth. If you have done this, you should feel bad and immediately switch ssh access to key authentication...
 
-7. `cft cheftacular_config [diff|display|sync|overwrite]` this command Allows you to interact with your complete cheftacular configuration, the union of all repository's cheftacular.ymls. 
+6. `cft cheftacular_config [diff|display|sync|overwrite]` this command Allows you to interact with your complete cheftacular configuration, the union of all repository's cheftacular.ymls. 
 
     1. `display` will show the current overall configuration for cheftacular.
 
@@ -353,29 +347,29 @@
 
     4. This command is aliased to `cc`
 
-8. `cft cheftacular_yml_help KEY` this commandallows you to get help on the meaning of each key in your cheftacular.yml overall config.
+7. `cft cheftacular_yml_help KEY` this commandallows you to get help on the meaning of each key in your cheftacular.yml overall config.
 
     1. This command can also by run with `cft yaml_help`.
 
     2. To examine nested keys, you can use colons inbetween the keys like cloud_authentication:rackspace:email
 
-9. `cft clean_cookbooks [force] [remove_cookbooks]` allows you to update the internal chef-repo's cookbooks easily. By default this script will force you to decide what to do with each cookbook individually (shows version numbers and whether to overwrite it to cookbooks or not).
+8. `cft clean_cookbooks [force] [remove_cookbooks]` allows you to update the internal chef-repo's cookbooks easily. By default this script will force you to decide what to do with each cookbook individually (shows version numbers and whether to overwrite it to cookbooks or not).
 
     1. `force` argument will cause the downloaded cookbooks to *always* overwrite the chef-repo's cookbooks as long as the downloaded cookbook has a higher version number.
 
     2. If you would like to remove all the cookbooks on the chef server, run `knife cookbook bulk delete '.*' -p -c ~/.chef/knife.rb`
 
-10. `cft cleanup_logs [DIRECTORIES_TO_NOT_DELETE]` this command allows you to clear your local log files
+9. `cft cleanup_logs [DIRECTORIES_TO_NOT_DELETE]` this command allows you to clear your local log files
 
     1. By default, this command will delete all the cheftacular directories in your log folder.
 
     2. This command supports a comma separated list of folders you don't want to delete.
 
-11. `cft clear_caches` this command allows you to clear all of your local caches.
+10. `cft clear_caches` this command allows you to clear all of your local caches.
 
     1. This command will force you to refetch all previously cached chef server data on the next `cft` run.
 
-12. `cft client_list` Allows you check the basic information for all the servers setup via chef. Shows the server's short name, its public ip address and roles (run_list) by default.
+11. `cft client_list` Allows you check the basic information for all the servers setup via chef. Shows the server's short name, its public ip address and roles (run_list) by default.
 
     1. `-v` option will make this command display the server's domain name, whether its password is stored on the chef server and what that password is.
 
@@ -389,7 +383,7 @@
 
     6. This command is aliased to `cft clients` and `cft cl`
 
-13. `cft cloud <FIRST_LEVEL_ARG> [<SECOND_LEVEL_ARG>[:<SECOND_LEVEL_ARG_QUERY>]*] ` this command handles talking to various cloud APIs. If no args are passed nothing will happen.
+12. `cft cloud <FIRST_LEVEL_ARG> [<SECOND_LEVEL_ARG>[:<SECOND_LEVEL_ARG_QUERY>]*] ` this command handles talking to various cloud APIs. If no args are passed nothing will happen.
 
     1. `domain` first level argument for interacting with cloud domains
 
@@ -485,7 +479,7 @@
 
         5. `bootstrap` captures the current computer's hostname and checks to see if a key matching this hostname exists on the cloud service. If the key does not exist, the command attempts to read the contents of the ~/.ssh/id_rsa.pub file and create a new key with that data and the hostname of the current computer. Run automatically when creating DigitalOcean servers. It's worth noting that if the computer's key already exists on DigitalOcean under a different name, this specific command will fail with a generic error. Please check your keys.
 
-14. `cft cloud_bootstrap NODE_NAME FLAVOR_NAME [DESCRIPTOR] [--with-dn DOMAIN]` uses a cloud api to create a server and attaches its DOMAIN_NAME to the TLD specified for that environment (IE: example-staging.com for staging)
+13. `cft cloud_bootstrap NODE_NAME FLAVOR_NAME [DESCRIPTOR] [--with-dn DOMAIN]` uses a cloud api to create a server and attaches its DOMAIN_NAME to the TLD specified for that environment (IE: example-staging.com for staging)
 
     1. If no DOMAIN_NAME is supplied it will use the node's NODE_NAME (IE: api01.example-staging.com)
 
@@ -497,15 +491,15 @@
 
     5. Aliased to `cft cb`
 
-15. `cft cloud_bootstrap_from_queue` uses a cloud api to create several servers. It is a wrapper around the cloud_bootstrap command that tries to queue server creation.
+14. `cft cloud_bootstrap_from_queue` uses a cloud api to create several servers. It is a wrapper around the cloud_bootstrap command that tries to queue server creation.
 
     1. This command cannot be called directly and can only be utilized from `cft environment boot`
 
-16. `cft compile_audit_log [clean]` compiles the audit logs in each environment's audit data bag a audit-log-CURRENTDAY.md file in the log folder of the application. Bear in mind that the bag can only hold 100K bytes and will need to have that data removed to store more than that.
+15. `cft compile_audit_log [clean]` compiles the audit logs in each environment's audit data bag a audit-log-CURRENTDAY.md file in the log folder of the application. Bear in mind that the bag can only hold 100K bytes and will need to have that data removed to store more than that.
 
-17. `cft compile_readme` compiles all documentation methods and creates a README.md file in the log folder of the application.
+16. `cft compile_readme` compiles all documentation methods and creates a README.md file in the log folder of the application.
 
-18. `cft create_git_key ID_RSA_FILE [OAUTH_TOKEN]` This command will update the default/authentication data bag with new credentials. The [ID_RSA_FILE](https://help.github.com/articles/generating-ssh-keys) needs to exist beforehand.
+17. `cft create_git_key ID_RSA_FILE [OAUTH_TOKEN]` This command will update the default/authentication data bag with new credentials. The [ID_RSA_FILE](https://help.github.com/articles/generating-ssh-keys) needs to exist beforehand.
 
     1. This command will upload both the private and public key to the data bag. The public key should be the one that matches the github user for your deployment github user.
 
@@ -513,9 +507,9 @@
 
     3. NOTE! The ID_RSA_FILE should be in your .chef folder in the root of your home directory!
 
-19. `cft disk_report` will fetch useful statistics from every server for every environment and output it into your log directory.
+18. `cft disk_report` will fetch useful statistics from every server for every environment and output it into your log directory.
 
-20. `cft environment boot|boot_without_deploy|destroy|destroy_raw_servers [SERVER_NAMES]` will boot / destroy the current environment
+19. `cft environment boot|boot_without_deploy|destroy|destroy_raw_servers [SERVER_NAMES]` will boot / destroy the current environment
 
     1. `boot` will spin up servers and bring them to a stable state. This includes setting up their subdomains for the target environment.
 
@@ -531,7 +525,7 @@
 
     7. Aliased to `cft e`
 
-21. `cft file NODE_NAME LOCATION_ALIAS MODE FILE_NAME` interacts with a file on the remote server
+20. `cft file NODE_NAME LOCATION_ALIAS MODE FILE_NAME` interacts with a file on the remote server
 
     1. `LOCATION_ALIAS` will be parsed as a path if it has backslash characters. Otherwise it will be parsed from your location_aliases hash in your cheftacular.yml
 
@@ -561,39 +555,39 @@
 
         1. `--save-to-file FILE_PATH` can also be used in the `fetch` context to specify where exactly to save the file and what to name it as.
 
-22. `cft fix_known_hosts [HOSTNAME]` this command will delete entries in your known_hosts file for all the servers that are in our system (ip addresses AND dns names)
+21. `cft fix_known_hosts [HOSTNAME]` this command will delete entries in your known_hosts file for all the servers that are in our system (ip addresses AND dns names)
 
     1. Passing in a hostname will make the command only remove entries with that hostname / ip specifically
 
     2. Aliased to `cft fkh`
 
-23. `cft full_bootstrap_from_queue` This command performs both ubuntu_bootstrap and chef_bootstrap.
+22. `cft full_bootstrap_from_queue` This command performs both ubuntu_bootstrap and chef_bootstrap.
 
     1. This command is run by `cft cloud_bootstrap` and should not be run on its own.
 
-24. `cft get_active_ssh_connections` will fetch the active ssh connections from every server and output it into your log directory.
+23. `cft get_active_ssh_connections` will fetch the active ssh connections from every server and output it into your log directory.
 
     1. This command runs on all servers in an environment by default
 
-25. `cft get_haproxy_log` this command will generate a haproxy html file for the load balancer(s) associated with a repository in the log directory. Opening this log file in the browser will show the status of that haproxy at the time of the log. 
+24. `cft get_haproxy_log` this command will generate a haproxy html file for the load balancer(s) associated with a repository in the log directory. Opening this log file in the browser will show the status of that haproxy at the time of the log. 
 
     1. In devops mode, this command will not do anything without the -R repository passed.
 
-26. `cft get_log_from_bag <NODE_NAME-COMMAND_TYPE>` this command grabs the latest command run log from the data bags and saves it to your log directory. There are different types of logs saved per server depending on command.
+25. `cft get_log_from_bag <NODE_NAME-COMMAND_TYPE>` this command grabs the latest command run log from the data bags and saves it to your log directory. There are different types of logs saved per server depending on command.
 
-27. `cft get_pg_pass ['clip']` command will output the current environment's pg_password to your terminal. Optionally you can pass in clip like `cft get_pg_pass clip` to have it also copy the pass to your clipboard.
+26. `cft get_pg_pass ['clip']` command will output the current environment's pg_password to your terminal. Optionally you can pass in clip like `cft get_pg_pass clip` to have it also copy the pass to your clipboard.
 
-28. `cft help COMMAND|MODE` this command returns the documentation for a specific command if COMMAND matches the name of a command. Alternatively, it can be passed `action|arguments|application|current|devops|stateless_action` to fetch the commands for a specific mode.Misspellings of commands will display near hits.
+27. `cft help COMMAND|MODE` this command returns the documentation for a specific command if COMMAND matches the name of a command. Alternatively, it can be passed `action|arguments|application|current|devops|stateless_action` to fetch the commands for a specific mode.Misspellings of commands will display near hits.
 
-29. `cft initialize_cheftacular_yml [application|TheCheftacularCookbook]` will create a cheftacular.yml file in your config folder (and create the config folder if it does not exist). If you already have a cheftacular.yml file in the config folder, it will create a cheftacular.example.yml file that will contain the new changes / keys in the latest cheftacular version.
+28. `cft initialize_cheftacular_yml [application|TheCheftacularCookbook]` will create a cheftacular.yml file in your config folder (and create the config folder if it does not exist). If you already have a cheftacular.yml file in the config folder, it will create a cheftacular.example.yml file that will contain the new changes / keys in the latest cheftacular version.
 
     1. If `TheCheftacularCookbook` is passed, the generated cheftacular.yml file will include the additional TheCheftacularCookbook keys.
 
     2. If `application` is passed, the generated cheftacular.yml file will look like one you could use in an application directory.
 
-30. `cft initialize_data_bag_contents ENVIRONMENT_NAME` will ensure the data bags always have the correct structure before each run. This command is run every time the gem is started and if called directly, will exit after completion.
+29. `cft initialize_data_bag_contents ENVIRONMENT_NAME` will ensure the data bags always have the correct structure before each run. This command is run every time the gem is started and if called directly, will exit after completion.
 
-31. `cft knife_upload [force]` will resync the chef-server with the local chef-repo code. This command is analog for `knife upload /`
+30. `cft knife_upload [force]` will resync the chef-server with the local chef-repo code. This command is analog for `knife upload /`
 
     1. The force option will add the force option to knife upload.
 
@@ -601,31 +595,31 @@
 
     3. Aliased to `cft ku`
 
-32. `cft list_toggleable_roles NODE_NAME` This command will allow you to see all toggleable roles for a node
+31. `cft list_toggleable_roles NODE_NAME` This command will allow you to see all toggleable roles for a node
 
-33. `cft location_aliases` will list all location aliases listed in your cheftacular.yml. These aliases can be used in the `cft file` command.
+32. `cft location_aliases` will list all location aliases listed in your cheftacular.yml. These aliases can be used in the `cft file` command.
 
     1. This command is aliased to `cft la`
 
-34. `cft pass NODE_NAME` will drop the server's sudo password into your clipboard. Useful for when you need to ssh into the server itself and try advanced linux commands
+33. `cft pass NODE_NAME` will drop the server's sudo password into your clipboard. Useful for when you need to ssh into the server itself and try advanced linux commands
 
-35. `cft reinitialize IP_ADDRESS NODE_NAME` will reconnect a server previously managed by chef to a new chef server. The node name MUST MATCH THE NODE'S ORIGINAL NODE NAME for the roles to be setup correctly.
+34. `cft reinitialize IP_ADDRESS NODE_NAME` will reconnect a server previously managed by chef to a new chef server. The node name MUST MATCH THE NODE'S ORIGINAL NODE NAME for the roles to be setup correctly.
 
-36. `cft remove_client NODE_NAME [destroy]` removes a client (and its node data) from the chef-server. It also removes its dns records from the cloud service (if possible). This should not be done lightly as you will have to wipe the server and trigger another chef-client run to get it to register again. Alternatively, you can run `cft reinitialize IP_ADDRESS NODE_NAME as well.
+35. `cft remove_client NODE_NAME [destroy]` removes a client (and its node data) from the chef-server. It also removes its dns records from the cloud service (if possible). This should not be done lightly as you will have to wipe the server and trigger another chef-client run to get it to register again. Alternatively, you can run `cft reinitialize IP_ADDRESS NODE_NAME as well.
 
     1. `destroy` deletes the server as well as removing it from the chef environment.
 
     2. This command is aliased to `cft remove_node` and `cft rc`
 
-37. `cft replication_status` will check the status of the database master and slaves in every environment. Also lists how far behind the slaves are from the master in milliseconds.
+36. `cft replication_status` will check the status of the database master and slaves in every environment. Also lists how far behind the slaves are from the master in milliseconds.
 
-38. `cft reset_bag BAG_NAME` this command allows you to reset a data bag item to an empty state. Run this on full data bags to clear them out. 
+37. `cft reset_bag BAG_NAME` this command allows you to reset a data bag item to an empty state. Run this on full data bags to clear them out. 
 
-39. `cft restart_swap` will restart the swap on every server that doesn't have swap currently on. Useful if you notice servers with no swap activated from `cft disk_report`
+38. `cft restart_swap` will restart the swap on every server that doesn't have swap currently on. Useful if you notice servers with no swap activated from `cft disk_report`
 
     1. There is no risk in running this command. Sometimes swap doesnt reactivate if the server was rebooted and this command fixes that.
 
-40. `cft role_toggle NODE_NAME ROLE_NAME activate|deactivate` This command will allow you to **toggle** roles on nodes without using `cft upload_nodes`
+39. `cft role_toggle NODE_NAME ROLE_NAME activate|deactivate` This command will allow you to **toggle** roles on nodes without using `cft upload_nodes`
 
     1. This command uses your *role_toggling:deactivated_role_suffix* attribute set in your cheftacular.yml to toggle the role, it checks to see if the toggled name exists then sets the node's run_list to include the toggled role
 
@@ -639,7 +633,7 @@
 
     4. Aliased to `cft rt`
 
-41. `cft rvm [COMMAND] [ADDITIONAL_COMMANDS]*` will run rvm commands on the remote servers. Output from this command for each server will go into your rvm directory under the log directory. Please refer to [the rvm help page](https://rvm.io/rvm) for more information on rvm commands.
+40. `cft rvm [COMMAND] [ADDITIONAL_COMMANDS]*` will run rvm commands on the remote servers. Output from this command for each server will go into your rvm directory under the log directory. Please refer to [the rvm help page](https://rvm.io/rvm) for more information on rvm commands.
 
     1. When no commands are passed, rvm will just run `rvm list` on each server on all servers in the current environment.
 
@@ -655,11 +649,11 @@
 
     7. `upgrade_rvm` will run `rvm get stable --auth-dotfiles` on all servers for the current environment. It will also check and attempt to upgrade pre 1.25 installations of RVM to 1.26+ (which requires a GPG key).
 
-42. `cft server_update [restart]` allows you to force update all nodes' packages for a specific environment. This should be done with caution as this *might* break something.
+41. `cft server_update [restart]` allows you to force update all nodes' packages for a specific environment. This should be done with caution as this *might* break something.
 
     1. `cft server_update restart` will prompt to ask if you also want to restart all servers in a rolling restart. This should be done with extreme caution and only in a worst-case scenario.
 
-43. `cft service [COMMAND] [SERVICE]` will run service commands on remote servers. This command only runs on the first server it comes across. Specify others with -n NODE_NAME.
+42. `cft service [COMMAND] [SERVICE]` will run service commands on remote servers. This command only runs on the first server it comes across. Specify others with -n NODE_NAME.
 
     1. When no commands are passed, the command will list all the services in the /etc/init directory
 
@@ -667,13 +661,13 @@
 
     3. When `restart|stop|start SERVICE` is passed, the command will attempt to restart|stop|start the service if it has a .conf file on the remote server in the /etc/init directory.
 
-44. `cft slack "MESSAGE" [CHANNEL]` will attempt to post the message to the webhook set in your cheftacular.yml. Slack posts to your default channel by default but if the CHANNEL argument is supplied the message will post there.
+43. `cft slack "MESSAGE" [CHANNEL]` will attempt to post the message to the webhook set in your cheftacular.yml. Slack posts to your default channel by default but if the CHANNEL argument is supplied the message will post there.
 
     1. NOTE: To prevent confusing spam from many possible sources, the username posted to slack will always be *Cheftacular*. This can be overloaded in the StatelessAction method "slack" but this is not recommended.
 
     2. Remember, if you have auditing turned on in your cheftacular.yml, you can track who sends what to slack.
 
-45. `cft test_env [TARGET_ENV] boot|destroy` will create (or destroy) the test nodes for a particular environment (defaults to staging, prod split-envs can be set with `-p`). Please read below for how TARGET_ENV works
+44. `cft test_env [TARGET_ENV] boot|destroy` will create (or destroy) the test nodes for a particular environment (defaults to staging, prod split-envs can be set with `-p`). Please read below for how TARGET_ENV works
 
     1. TARGET_ENV changes functionality depending on the overall (like staging / production) environment
 
@@ -683,11 +677,11 @@
 
         3. The default tld used should change depending on which environment you are booting / destroying. This is set in the environment's config data bag under the tld key
 
-46. `cft ubuntu_bootstrap_from_queue` This command will bring a fresh server to a state where chef-client can be run on it via `cft chef-bootstrap`. It should be noted that it is in this step where a server's randomized deploy_user sudo password is generated.
+45. `cft ubuntu_bootstrap_from_queue` This command will bring a fresh server to a state where chef-client can be run on it via `cft chef-bootstrap`. It should be noted that it is in this step where a server's randomized deploy_user sudo password is generated.
 
-47. `cft update_cheftacular` this command attempts to update cheftacular to the latest version.
+46. `cft update_cheftacular` this command attempts to update cheftacular to the latest version.
 
-48. `cft update_cloudflare_dns_from_cloud [skip_update_tld]` command will force a full dns update for cloudflare. 
+47. `cft update_cloudflare_dns_from_cloud [skip_update_tld]` command will force a full dns update for cloudflare. 
 
     1. It will ensure all the subdomain entries are correct (based on the contents of the addresses data bag) and update them if they are not. It will also create the local subdomain for the entry as well if it does exist and point it to the correct private address for an environment.
 
@@ -695,13 +689,13 @@
 
     3. The argument `skip_update_tld` will stop the long process of checking and updating all the server domains _before_ cloudflare is updated. Only skip if you believe your domain info on your cloud is accurate.
 
-49. `cft update_cookbook [COOKBOOK_NAME] [INSTALL_VERSION]` allows you to specifically update a single cookbook
+48. `cft update_cookbook [COOKBOOK_NAME] [INSTALL_VERSION]` allows you to specifically update a single cookbook
 
     1. This command passed with no arguments will update TheCheftacularCookbook
 
     2. Aliased to `cft uc`
 
-50. `cft update_split_branches` will perform a series of git commands that will merge all the split branches for your split_branch enabled repositories with what is currently on master and push them.
+49. `cft update_split_branches` will perform a series of git commands that will merge all the split branches for your split_branch enabled repositories with what is currently on master and push them.
 
     1. Repository must be set with `-R REPOSITORY_NAME` for this command to work.
 
@@ -711,9 +705,9 @@
 
     4. This command will return a helpful error statement if you attempt to run the command with changes to your current working directory. You must commit these changes before running this command.
 
-51. `cft update_tld TLD` command will force a full dns update for a tld in the preferred cloud. It will ensure all the subdomain entries are correct (based on the contents of the addresses data bag) and update them if they are not. It will also create the local subdomain for the entry as well if it does exist and point it to the correct private address.
+50. `cft update_tld TLD` command will force a full dns update for a tld in the preferred cloud. It will ensure all the subdomain entries are correct (based on the contents of the addresses data bag) and update them if they are not. It will also create the local subdomain for the entry as well if it does exist and point it to the correct private address.
 
-52. `cft upload_nodes` This command will resync the chef server's nodes with the data in our chef-repo/node_roles. 
+51. `cft upload_nodes` This command will resync the chef server's nodes with the data in our chef-repo/node_roles. 
 
     1. This command changes behavior depending on several factors about both your mode and the state of your environment
 
@@ -727,10 +721,10 @@
 
     4. Aliased to `cft un`
 
-53. `cft upload_roles` This command will resync the chef server's roles with the data in the chef-repo/roles.
+52. `cft upload_roles` This command will resync the chef server's roles with the data in the chef-repo/roles.
 
     1. Aliased to `cft ur`
 
-54. `cft version` this command prints out the current version of cheftacular.
+53. `cft version` this command prints out the current version of cheftacular.
 
     1. Aliased to `cft v`

data/lib/cheftacular/{stateless_actions → actions}/backups.rb

@@ -2,8 +2,8 @@
 class Cheftacular
   class StatelessActionDocumentation
     def backups
-      @config['documentation']['stateless_action'][__method__] ||= {}
-      @config['documentation']['stateless_action'][__method__]['long_description'] = [
+      @config['documentation']['action'][__method__] ||= {}
+      @config['documentation']['action'][__method__]['long_description'] = [
         "`cft backups [activate|deactivate|fetch|load|restore]` this command " +
         "sets the fetch_backups and restore_backups flags in your config data bag for an environment. " +
         "These can be used to give application developers a way to trigger / untrigger restores in an environment",
@@ -18,13 +18,15 @@ class Cheftacular
           "    4. `load` will fetch the latest backup from the production primary **if it doesn't already exist on " +
           "the server** and run the _backup loading command_ to load this backup into the env.",
 
-          "    5. `restore` will simply just run the _backup loading command_ to load the latest backup onto the server."
+          "    5. `restore` will simply just run the _backup loading command_ to load the latest backup onto the server.",
+
+          "    6. `status` will display the current state of the backups",
+
+          "    6. By default, the backups command will use the context of your current environment to trigger backup related commands."
         ]
       ]
 
-      @config['documentation']['stateless_action'][__method__]['short_description'] = 'Runs various backup commands on your current environment'
-
-      @config['documentation']['application'][__method__] = @config['documentation']['stateless_action'][__method__]
+      @config['documentation']['action'][__method__]['short_description'] = 'Runs various backup commands on your current environment'
     end
   end
 
@@ -32,7 +34,7 @@ class Cheftacular
     def backups command=''
       command = ARGV[1] if command.blank?
 
-      raise "Unsupported command (#{ command }) for cft backups" unless command =~ /activate|deactivate|fetch|load|restore/
+      raise "Unsupported command (#{ command }) for cft backups" unless command =~ /activate|deactivate|fetch|load|restore|status/
 
       self.send("backups_#{ command }")
     end
@@ -66,9 +68,15 @@ class Cheftacular
     end
 
     def backups_restore
+      backup_mode = case @config['getter'].get_current_database
+                    when 'postgresql' then 'pg'
+                    when 'mongodb'    then 'mongo'
+                    end
+
       target_db_primary, nodes = @config['getter'].get_db_primary_node_and_nodes
-      applications_as_string   = @config['getter'].get_repo_names_for_repositories.keys.join(',')
-      env_pg_pass              = @config[@options['env']]['chef_passwords_bag_hash']['pg_pass']
+      applications_as_string   = @config['getter'].get_repo_names_for_repositories({ database: @config['getter'].get_current_database }).keys.join(',')
+      env_db_pass              = @config[@options['env']]['chef_passwords_bag_hash']["#{ backup_mode }_pass"]
+      env_db_mode              = @config['getter'].get_current_database
 
       options, locs, ridley, logs_bag_hash, pass_bag_hash, bundle_command, cheftacular, passwords = @config['helper'].set_local_instance_vars
 
@@ -79,7 +87,7 @@ class Cheftacular
 
         puts("Beginning db_backup_run for #{ n.name } (#{ n.public_ipaddress }) for env #{ options['env'] }") unless options['quiet']
 
-        start_db_backup_restore( n.name, n.public_ipaddress, options, locs, cheftacular, passwords, applications_as_string, env_pg_pass, ruby_command )
+        start_db_backup_restore( n.name, n.public_ipaddress, options, locs, cheftacular, passwords, applications_as_string, env_db_pass, ruby_command, env_db_mode )
       end
     end
 
@@ -92,14 +100,12 @@ class Cheftacular
       file_scp_execute(target_db_primary, 'scp', full_backup_dir, status_hash['latest_backup']['filename'])
     end
 
-    private
+    def backups_status
+      backups_check_current_status
+    end
 
     def backups_toggle_setting restore_backup, fetch_backup
-      initial_fetch_backup   = @config[@options['env']]['config_bag_hash'][@options['sub_env']]['fetch_backups']
-      initial_restore_backup = @config[@options['env']]['config_bag_hash'][@options['sub_env']]['restore_backups']
-
-      puts "For #{ @options['env'] } (sub-env: #{ @options['sub_env'] }) fetch backups was set to " +
-        "#{ initial_fetch_backup ? 'on' : 'off' } and restoring backups was set to #{ initial_restore_backup ? 'on' : 'off' }"
+      backups_check_current_status
 
       puts "For #{ @options['env'] } (sub-env: #{ @options['sub_env'] }) fetch backups is now set to " +
         "#{ fetch_backup ? 'on' : 'off' } and restoring backups is now set to #{ restore_backup ? 'on' : 'off' }"
@@ -116,6 +122,14 @@ class Cheftacular
       @config['action'].deploy
     end
 
+    def backups_check_current_status
+      initial_fetch_backup   = @config[@options['env']]['config_bag_hash'][@options['sub_env']]['fetch_backups']
+      initial_restore_backup = @config[@options['env']]['config_bag_hash'][@options['sub_env']]['restore_backups']
+
+      puts "For #{ @options['env'] } (sub-env: #{ @options['sub_env'] }) fetch backups is currently set to " +
+        "#{ initial_fetch_backup ? 'on' : 'off' } and restoring backups is currently set to #{ initial_restore_backup ? 'on' : 'off' }"
+    end
+
     def backups_get_status_hash_from_backupmaster mode='backups_load', status_hash={}
       backup_env = @config['cheftacular']['backup_config']['global_backup_environ']
 
@@ -221,7 +235,7 @@ module SSHKit
         puts "Finished transferring #{ full_backup_path } to #{ name }(#{ ip_address })..."
       end
 
-      def start_db_backup_restore name, ip_address, options, locs, cheftacular, passwords, applications_as_string, env_pg_pass, ruby_command, out=''
+      def start_db_backup_restore name, ip_address, options, locs, cheftacular, passwords, applications_as_string, env_db_pass, ruby_command, env_db_mode, out=''
         log_loc, timestamp = set_log_loc_and_timestamp(locs)
 
         puts "Beginning backup run on #{ name } (#{ ip_address }), this command may take a while to complete..."
@@ -229,8 +243,8 @@ module SSHKit
         case cheftacular['backup_filesystem']
         when 'backup_gem'
           command = cheftacular['backup_config']['backup_load_command']
-          command = command.gsub('ENVIRONMENT', options['env']).gsub('APPLICATIONS', applications_as_string).gsub('PG_PASS', env_pg_pass)
-          command = command.gsub('RUBY_COMMAND', ruby_command )
+          command = command.gsub('ENVIRONMENT', options['env']).gsub('APPLICATIONS', applications_as_string).gsub('DB_PASS', env_db_pass)
+          command = command.gsub('RUBY_COMMAND', ruby_command ).gsub('MODE', env_db_mode)
 
           out << sudo_capture( passwords[ip_address], command )
         when 'raw'

data/lib/cheftacular/actions/console.rb

@@ -60,7 +60,7 @@ class Cheftacular
       true_env = @config['dummy_sshkit'].get_true_environment run_list, @config['cheftacular']['run_list_environments'][@options['env']], @options['env']
 
       #the >/dev/tty after the ssh block redirects the full output to stdout, not /dev/null where it normally goes  
-      `ssh -oStrictHostKeyChecking=no -tt #{ @config['cheftacular']['deploy_user'] }@#{ ip_address } "cd #{ app_loc } && RAILS_ENV=#{ true_env } #{ @config['bundle_command'] } exec rails c" > /dev/tty`
+      `ssh #{ Cheftacular::SSH_INLINE_VARS } -tt #{ @config['cheftacular']['deploy_user'] }@#{ ip_address } "cd #{ app_loc } && RAILS_ENV=#{ true_env } #{ @config['bundle_command'] } exec rails c" > /dev/tty`
     end
 
     def start_console_nodejs

data/lib/cheftacular/actions/run.rb

@@ -16,7 +16,9 @@ class Cheftacular
           "It prepends bundle exec to your command for rails stack repositories",
 
           "    4. IMPORTANT NOTE: You cannot run `cft run rake -T` as is, you have to enclose any command that uses command line dash " +
-          'arguments in quotes like `cft run "rake -T"`'
+          'arguments in quotes like `cft run "rake -T"`',
+
+          "    5. Can also be used to run meteor commands and is aliased to `cft meteor`"
         ]
       ]
 
@@ -34,33 +36,15 @@ class Cheftacular
     end
 
     def run_ruby_on_rails command
-      nodes   = @config['getter'].get_true_node_objects
-
-      #must have rails stack to run migrations and not be a db, only want ONE node
-      nodes = @config['parser'].exclude_nodes( nodes, [{ unless: "role[#{ @options['role'] }]" }], !@options['run_on_all'] )
-
-      nodes = @config['parser'].exclude_nodes( nodes, [{ if: "role[#{ @options['negative_role'] }]" }]) if @options['negative_role']
-
-      #this must always precede on () calls so they have the instance variables they need
-      options, locs, ridley, logs_bag_hash, pass_bag_hash, bundle_command, cheftacular, passwords = @config['helper'].set_local_instance_vars
-
-      on ( nodes.map { |n| @config['cheftacular']['deploy_user'] + "@" + n.public_ipaddress } ) do |host|
-        n = get_node_from_address(nodes, host.hostname)
-
-        puts("Beginning task run for #{ n.name } (#{ n.public_ipaddress }) on role #{ options['role'] }") unless options['quiet']
-
-        log_data, timestamp, exit_status = start_task( n.name, n.public_ipaddress, n.run_list, "#{ bundle_command } exec #{ command }", options, locs, cheftacular, passwords)
-
-        logs_bag_hash["#{ n.name }-#{ __method__ }"] = { "text" => log_data.scrub_pretty_text, "timestamp" => timestamp, "exit_status" => exit_status }
-      end
-
-      @config['ChefDataBag'].save_logs_bag
-
-      @config['helper'].send_log_bag_hash_slack_notification(logs_bag_hash, __method__, 'Failing command detected, exiting...')
+      run_command(command, __method__.to_s, "#{ @config['bundle_command'] } exec")
     end
 
     def run_nodejs command
-      raise "Not yet implemented"
+      self.send("run_#{ @config['getter'].get_current_sub_stack }", command)
+    end
+
+    def run_meteor command
+      run_command(command, __method__.to_s, '/usr/local/bin/meteor', true)
     end
 
     def run_wordpress command
@@ -72,9 +56,34 @@ class Cheftacular
     end
 
     def run_ command
-      puts "Run method tried to run a command for the role \"#{ @options['role'] }\" but it doesn't appear to have a repository set! Skipping..."
+      puts "Run method tried to run a command for the role \"#{ @options['role'] }\" but it doesn't appear to have a repository or stack set! Skipping..."
 
       return false
     end
+
+    alias_method :meteor, :run
+
+    private
+
+    def run_command command, descriptor, executable, sudo=false
+      nodes = @config['getter'].get_current_role_nodes
+
+      #this must always precede on () calls so they have the instance variables they need
+      options, locs, ridley, logs_bag_hash, pass_bag_hash, bundle_command, cheftacular, passwords = @config['helper'].set_local_instance_vars
+
+      on ( nodes.map { |n| @config['cheftacular']['deploy_user'] + "@" + n.public_ipaddress } ) do |host|
+        n = get_node_from_address(nodes, host.hostname)
+
+        puts("Beginning #{ descriptor } run for #{ n.name } (#{ n.public_ipaddress }) on role #{ options['role'] }") unless options['quiet']
+
+        log_data, timestamp, exit_status = start_task( n.name, n.public_ipaddress, n.run_list, "#{ executable } #{ command }", options, locs, cheftacular, passwords, sudo)
+
+        logs_bag_hash["#{ n.name }-#{ descriptor }"] = { "text" => log_data.scrub_pretty_text, "timestamp" => timestamp, "exit_status" => exit_status }
+      end
+
+      @config['ChefDataBag'].save_logs_bag
+
+      @config['helper'].send_log_bag_hash_slack_notification(logs_bag_hash, __method__, 'Failing command detected, exiting...')
+    end
   end
 end

data/lib/cheftacular/actions/tail.rb

@@ -59,6 +59,12 @@ class Cheftacular
       `ssh -oStrictHostKeyChecking=no -tt #{ @config['cheftacular']['deploy_user'] }@#{ ip_address } "#{ @config['helper'].sudo(ip_address) } tail -f #{ log_loc } #{ get_tail_grep_string(pattern_to_match) }" > /dev/tty`
     end
 
+    def start_tail_nodejs ip_address, run_list, pattern_to_match
+      log_loc = "/var/log/syslog"
+
+      `ssh #{ Cheftacular::SSH_INLINE_VARS } -tt #{ @config['cheftacular']['deploy_user'] }@#{ ip_address } "#{ @config['helper'].sudo(ip_address) } tail -f #{ log_loc } #{ get_tail_grep_string(pattern_to_match) }" > /dev/tty`
+    end
+
     def get_tail_grep_string pattern_to_match=''
       "| grep -i -E \\\"#{ pattern_to_match }\\\"" unless pattern_to_match.blank?
     end

data/lib/cheftacular/cheftacular.rb

@@ -27,9 +27,17 @@ require 'csv'
 Dir["#{File.dirname(__FILE__)}/../**/*.rb"].each { |f| require f }
 
 class Cheftacular
+  SSH_INLINE_VARS = '-oStrictHostKeyChecking=no -oServerAliveInterval=60'
+
   def initialize options={'env'=>'staging'}, config={}
     @options, @config                = options, config
+    
     SSHKit.config.format             = :blackhole
+    SSHKit::Backend::Netssh.configure do |ssh|
+      ssh.connection_timeout = 30
+      ssh.ssh_options = { keepalive: true, keepalive_interval: 60 }
+    end
+
     Excon.defaults[:ssl_verify_peer] = false #https://github.com/excon/excon/issues/479 # issues with cert bundle chains
     #Fog::Logger[:warning]            = nil
     @config['start_time']            = Time.now

data/lib/cheftacular/getter.rb

@@ -91,6 +91,10 @@ class Cheftacular
       get_current_repo_config['stack']
     end
 
+    def get_current_sub_stack
+      get_current_repo_config['sub_stack']
+    end
+
     def get_current_database
       get_current_repo_config['database']
     end
@@ -157,8 +161,17 @@ class Cheftacular
       ret
     end
 
-    def get_repo_names_for_repositories ret={}
+    def get_repo_names_for_repositories restrict_to={}, ret={}
       @config['cheftacular']['repositories'].each_pair do |name, repo_hash|
+        unless restrict_to.empty?
+          skip = false
+          restrict_to.each_pair do |key, val|
+            skip = true if repo_hash[key.to_s] == val
+          end
+
+          next if skip
+        end
+
         ret[repo_hash['repo_name']]         = repo_hash
         
         ret[repo_hash['repo_name']]['role'] = name
@@ -173,5 +186,13 @@ class Cheftacular
 
       ret
     end
+
+    def get_current_role_nodes
+      nodes = @config['parser'].exclude_nodes( @config['getter'].get_true_node_objects, [{ unless: "role[#{ @options['role'] }]" }], !@options['run_on_all'] )
+
+      nodes = @config['parser'].exclude_nodes( nodes, [{ if: "role[#{ @options['negative_role'] }]" }]) if @options['negative_role']
+
+      nodes
+    end
   end
 end

data/lib/cheftacular/helper.rb

@@ -259,7 +259,7 @@ class Cheftacular
     end
 
     def slack_current_deploy_arguments
-      msg  = "#{ Socket.gethostname } just set for the repository #{ @config['getter'].get_repository_from_role_name(@options['role']) }:\n"
+      msg  = "#{ Socket.gethostname }(#{ @config['locs']['root'] }) just set for the repository #{ @config['getter'].get_repository_from_role_name(@options['role']) }:\n"
       msg << "the organization to #{ @options['deploy_organization'] }\n" if @options['deploy_organization']
       msg << "the revision to #{ @options['target_revision'] }\n"         if @options['target_revision']
       msg << "In the environment: #{ @options['env'] }"

data/lib/cheftacular/version.rb

@@ -1,5 +1,5 @@
 class Cheftacular
   #major_version.minor_version.bugfixes
-  VERSION      = "2.13.1"
+  VERSION      = "2.13.2"
   RUBY_VERSION = "2.2.2"
 end

data/lib/cloud_interactor/domain/list_records.rb

@@ -19,6 +19,16 @@ class CloudInteractor
       @main_obj['output']["records_for_#{ @main_obj["specific_#{ IDENTITY }"].last['domain'] }"] = @main_obj["specific_#{ IDENTITY }"].last['records']
 
       ap(@main_obj["specific_#{ IDENTITY }"].last['records']) if output
+    rescue Excon::Errors::Timeout => e
+      tries ||= 3
+      puts "Issue reading records for the domain #{ args['domain'] }! Error: #{e}. Trying #{tries} more times."
+      tries -= 1
+      if tries > 0
+        sleep(15)
+        retry
+      else
+        false
+      end
     end
   end
 end

data/lib/cloud_interactor/domain/update_record.rb

@@ -26,17 +26,31 @@ class CloudInteractor
 
         case @options['route_dns_changes_via']
         when /rackspace|dnsimple/
-          specific_record.type  = args['type']
-          specific_record.value = args['target_ip']
-          specific_record.ttl   = args['ttl']
-
-          specific_record.save
+          begin
+            specific_record.type  = args['type']
+            specific_record.value = args['target_ip']
+            specific_record.ttl   = args['ttl']
+
+            specific_record.save
+          rescue Fog::Errors::Error => e
+            tries ||= 3
+            puts "Issue updating records for the domain #{ args[IDENTITY.singularize] }! Error: #{e}. Trying #{tries} more times."
+            tries -= 1
+            if tries > 0
+              sleep(15)
+              retry
+            else
+              false
+            end
+          end
         else
           raise "Unsupported action #{ __method__ } for #{ @options['preferred_cloud'] }. Please create an issue on github or submit a PR to fix this issue."
         end
 
         puts "(#{ IDENTITY.capitalize }) Updated #{ args['subdomain'] } (#{ args['target_ip'] }) to #{ args[IDENTITY.singularize] } (#{ args['target_domain'] })..."
       else
+        tries = 3
+        
         create_record [ args ]
       end
     end

data/lib/cloud_interactor/helpers.rb

@@ -19,6 +19,16 @@ class CloudInteractor
       @main_obj[identity] = JSON.parse(@classes['auth'].auth_service(resource).instance_eval(identity).to_json)
 
       ap(@main_obj[identity]) if output && !@options['in_scaling']
+    rescue Excon::Errors::Timeout => e
+      tries ||= 3
+      puts "Issue reading data for the #{ identity.capitalize }! Error: #{e}. Trying #{tries} more times."
+      tries -= 1
+      if tries > 0
+        sleep(15)
+        retry
+      else
+        false
+      end
     end
 
     def generic_read_parse args, identity, output=true, mode='name', search_key='name'

data/lib/cloud_interactor/version.rb

@@ -1,4 +1,4 @@
 class CloudInteractor
   #major_version.minor_version.bugfixes
-  VERSION      = "1.1.0"
+  VERSION      = "1.1.1"
 end

data/lib/sshkit/actions/start_task.rb

@@ -1,7 +1,7 @@
 module SSHKit
   module Backend
     class Netssh
-      def start_task name, ip_address, run_list, command, options, locs, cheftacular, passwords, out=""
+      def start_task name, ip_address, run_list, command, options, locs, cheftacular, passwords, sudo=false, out=""
         log_loc, timestamp = set_log_loc_and_timestamp(locs)
         true_env = get_true_environment run_list, cheftacular['run_list_environments'][options['env']], options['env']
 
@@ -15,11 +15,12 @@ module SSHKit
           return ['', timestamp]
         end
 
-        capture_args = ["RAILS_ENV=#{ true_env }"]
+        capture_args =  []
+        capture_args << ["RAILS_ENV=#{ true_env }"] if cheftacular['repositories'][options['role']]['stack'] == 'ruby_on_rails'
         capture_args << command.split(' ')
 
         within target_loc do
-          out << capture( *capture_args.flatten )
+          out << (sudo ? sudo_capture(passwords[ip_address], *capture_args.flatten) : capture( *capture_args.flatten ))
         end
 
         ::File.open("#{ log_loc }/#{ name }-task-#{ timestamp }.txt", "w") {|f| f.write(out.scrub_pretty_text) } if options['debug']

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cheftacular
 version: !ruby/object:Gem::Version
-  version: 2.13.1
+  version: 2.13.2
 platform: ruby
 authors:
 - Louis Alridge
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-02-02 00:00:00.000000000 Z
+date: 2016-03-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hashie
@@ -252,6 +252,7 @@ files:
 - lib/cheftacular.rb
 - lib/cheftacular/README.md
 - lib/cheftacular/action.rb
+- lib/cheftacular/actions/backups.rb
 - lib/cheftacular/actions/check.rb
 - lib/cheftacular/actions/console.rb
 - lib/cheftacular/actions/db_console.rb
@@ -281,7 +282,6 @@ files:
 - lib/cheftacular/stateless_action.rb
 - lib/cheftacular/stateless_actions/add_ssh_key_to_bag.rb
 - lib/cheftacular/stateless_actions/arguments.rb
-- lib/cheftacular/stateless_actions/backups.rb
 - lib/cheftacular/stateless_actions/bootstrappers/centos_bootstrap_from_queue.rb
 - lib/cheftacular/stateless_actions/bootstrappers/coreos_bootstrap_from_queue.rb
 - lib/cheftacular/stateless_actions/bootstrappers/fedora_bootstrap_from_queue.rb