- Dec 20, 2021
-
-
Alexandre MERLIN authored
-
- Dec 15, 2021
-
-
Alexandre MERLIN authored
Simplification de la CLI See merge request !30
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
- Dec 13, 2021
-
-
Alexandre MERLIN authored
-
- Dec 08, 2021
-
-
Alexandre MERLIN authored
-
- Dec 07, 2021
-
-
Alexandre MERLIN authored
Permet d'utiliser --vlan DEFAULT avec kadeploy See merge request !31
-
- Dec 06, 2021
-
-
Alexandre MERLIN authored
-
- Nov 25, 2021
-
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
- Nov 24, 2021
-
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
This reverts commit 8398c327.
-
Alexandre MERLIN authored
-
- Nov 23, 2021
-
-
Alexandre MERLIN authored
Default option for cli See merge request !29
-
- Nov 22, 2021
-
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
- To force unsetting an option, "none" can be used (eg: "-k none" or "-r none") - When -f or -m is not specify, the default option "file" will be tried - if there is an environment variable (with syntax $ENV_VAR), it will be expanded - So, for an operation without -m or -f, using "file: $MY_MACHINE_FILE" will try to read from the file pointed by the environment varirable, if the variable does not exist, file is blank and kadeploy do not try to read anything (the deployment will fail with "no node chosen") - key option now works with "~" - Also, an error is now raised when both -f and -m are used
-
- Nov 18, 2021
-
-
Alexandre MERLIN authored
-
- Oct 28, 2021
-
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
Kadeploy 3.7 See merge request !28
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
Previously, all the nodes were changed to the rebooted/deployed state at the end of the full reboot/deploy operation. Now, the state of each node is updated as soon as kadeploy sees the node is here after the last wait_reboot operation. So the updated nodes are immediately available to be part of another kadeploy operation. We are still waiting for all nodes to be rebooted/deployed if there is a custom operation after the wait_reboot.
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
- Oct 19, 2021
-
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
-
Alexandre MERLIN authored
- Injecting custom variables from the cli with --custom-variable KEY=VALUE (can be specify multiple times) or from the env description with the "custom_variables" hash or in the cluster configuration with the hash of the same name. - The custom variables are accessible in kadeploy scripts by prefixing them by "KADEPLOY_". (eg: KADEPLOY_DEBUG) - The name of the variable and the value must be a string. - Priority of variables: CLI > env description > cluster configuration. A warning appears when a custom variable is overwrite. (eg: "Custom Variables from the environement overwrite by the client: DEBUG.") - Some name are reserved by kadeploy and can't be overwrite. An error is thrown when trying to name a custom variable with such name from the CLI. (eg: "You cannot overwrite Kadeploy variables: CLUSTER.")
-