You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Note: in QUADS `1.1.4` you can change any of these values selectively via the `--mod-cloud` command [described below](#modifying-cloud-level-attributes).
590
+
588
591
- Now that you've defined your new cloud you'll want to allocate machines and a schedule.
589
592
- We're going to find the first 20 Dell r620's and assign them as an example.
* In some scenarios you may wish to interrogate or modify values within MongoDB. You should be careful doing this and have good backups in place. Generally, we will try to implement data, object and document modification needs through quads-cli so you don't need to do this but sometimes it's useful for troubleshooting or other reasons.
950
973
974
+
***NOTE**: For most of the below examples usage of `quads-cli --mod-cloud` supplants the need for making any changes in MongoDB post QUADS version `1.1.4`. We'll leave these examples below for posterity or in the case they can be modeled to do something else useful otherwise.
975
+
951
976
* Example: Toggling the `wipe:` cloud value that determines whether new systems entering an environment should be reprovisioned or not. In this example `cloud02` has the value of `wipe: 0` and we want to change this within Mongodb.
0 commit comments