| 2016-02-01 15:35:33 |
Omar Rivera |
bug |
|
|
added bug |
| 2016-02-01 15:36:33 |
Omar Rivera |
fuel: assignee |
|
Omar Rivera (gomarivera) |
|
| 2016-02-01 17:02:32 |
Vitalii Myhal |
description |
In order to upgrade deployed cluster that is in operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings).
Add --force flag for `fuel deploy-changes` command The flag allows to apply the changes to the cluster if the cluster is in the operational state. This allows you to deploy the changes without the reprovisioning procedure. Example: `fuel deploy-changes --env <env_id> --force`
Optional flag '--force' is added to the commands below: fuel --env <env_id> settings --upload --force fuel env --env <env_id> --attributes --upload --force This flag is handled by API here: clusters/<id>/attributes/?force=1
Adds ability to force update env attrs In order to upgrade deployed cluster that is in operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings). Optional flag '--force' is added to the commands below: fuel --env <env_id> settings --upload --force fuel env --env <env_id> --attributes --upload --force This flag is handled by API here: clusters/<id>/attributes/?force=1 |
In order to upgrade deployed cluster that is in an operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings).
Add --force flag for `fuel deploy-changes` command. The flag allows applying the changes to the cluster if the cluster is in the operational state. This allows you to deploy the changes without the reprovisioning procedure. Example: `fuel deploy-changes --env <env_id> --force`
Optional flag '--force' is added to the commands below:
fuel --env <env_id> settings --upload --force
fuel env --env <env_id> --attributes --upload --force
This flag is handled by API here: clusters/<id>/attributes/?force=1 |
|
| 2016-02-01 17:08:03 |
Vitalii Myhal |
description |
In order to upgrade deployed cluster that is in an operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings).
Add --force flag for `fuel deploy-changes` command. The flag allows applying the changes to the cluster if the cluster is in the operational state. This allows you to deploy the changes without the reprovisioning procedure. Example: `fuel deploy-changes --env <env_id> --force`
Optional flag '--force' is added to the commands below:
fuel --env <env_id> settings --upload --force
fuel env --env <env_id> --attributes --upload --force
This flag is handled by API here: clusters/<id>/attributes/?force=1 |
In order to upgrade deployed cluster that is in an operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings).
Add --force flag for `fuel deploy-changes` command. The flag allows applying the changes to the cluster if the cluster is in the operational state. This allows you to deploy the changes without the reprovisioning procedure. Example:
fuel deploy-changes --env <env_id> --force
Optional flag '--force' is added to the commands below:
fuel settings --env <env_id> --upload --force
fuel env --env <env_id> --attributes --upload --force
This flag is handled by API here: clusters/<id>/attributes/?force=1 |
|
| 2016-02-01 17:14:44 |
Omar Rivera |
tags |
|
customer-found |
|
| 2016-02-01 19:58:57 |
Omar Rivera |
description |
In order to upgrade deployed cluster that is in an operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings).
Add --force flag for `fuel deploy-changes` command. The flag allows applying the changes to the cluster if the cluster is in the operational state. This allows you to deploy the changes without the reprovisioning procedure. Example:
fuel deploy-changes --env <env_id> --force
Optional flag '--force' is added to the commands below:
fuel settings --env <env_id> --upload --force
fuel env --env <env_id> --attributes --upload --force
This flag is handled by API here: clusters/<id>/attributes/?force=1 |
In order to upgrade deployed cluster that is in operational state without re-provisioning it, we need a possibility to forcefully update cluster attributes (aka cluster/environment settings).
Optional flag '--force' is added to the commands below:
fuel --env <env_id> settings --upload --force
fuel env --env <env_id> --attributes --upload --force
This flag is handled by API here: clusters/<id>/attributes/?force=1 |
|
| 2016-02-01 19:59:21 |
Omar Rivera |
summary |
Add capability to update the release attributes |
Adds ability to force update environment attributes |
|
| 2016-02-02 11:28:23 |
Alexander Kislitsky |
tags |
customer-found |
area-python customer-found feature |
|
| 2016-02-02 11:28:26 |
Alexander Kislitsky |
fuel: milestone |
|
9.0 |
|
| 2016-02-02 11:28:32 |
Alexander Kislitsky |
fuel: importance |
Undecided |
Medium |
|
| 2016-02-02 11:28:36 |
Alexander Kislitsky |
fuel: status |
New |
Confirmed |
|
| 2016-02-02 17:48:52 |
Vitalii Myhal |
fuel: assignee |
Omar Rivera (gomarivera) |
Vitalii Myhal (xmig) |
|
| 2016-02-02 17:51:13 |
Vitalii Myhal |
fuel: status |
Confirmed |
In Progress |
|
| 2016-03-17 14:51:36 |
Vitalii Myhal |
fuel: status |
In Progress |
Fix Committed |
|
| 2016-06-30 11:34:11 |
Alisa Tselovalnikova |
fuel: status |
Fix Committed |
Fix Released |
|
