fugue2 update

Usage

fugue2 update <ALIAS or FID> <COMPOSITION.lw> [flags]

Arguments

<ALIAS or FID>
Alias or FID of the process to update
<COMPOSITION.LW>
Composition file to update the process with

Options

Global options are detailed here.

--dry-run
Update a composition in dry-run mode.
-h | --help
Show help text for update.
-y | --yes
Suppress confirmation dialogs.

Definition

The update command updates the infrastructure of a running process to match the infrastructure specified in a given composition.

When the update command is executed, the CLI compiles the composition and reports any errors, then sends a request to the Conductor to update the process’s infrastructure.

The Fugue Conductor then does the following:

  • Compares the process’s infrastructure to the infrastructure declared in the compiled, updated composition
  • Determines the infrastructure operations required to make the process match the composition
  • Performs the infrastructure operations

Examples

To modify a running process, edit the composition file and execute update:

fugue2 update myProcess ResourceGroup.lw

The Fugue CLI asks you to confirm that you want to update the specified process:

[ fugue update ] Updating process: myProcess with ResourceGroup.lw.

[ WARN ] Are you sure you want to update process myProcess with ResourceGroup.lw? [y/N] y

Upon confirmation, the CLI sends a request to the Conductor asking it to resume the process. When the request is accepted, the CLI displays a success message and updated status details:

Compiling Ludwig file ResourceGroup.lw
[ OK ] Successfully compiled. No errors.

Requesting the Conductor to update process myProcess with ResourceGroup.lw ...

[ DONE ] Process myProcess updated with ResourceGroup.lw.

{
  "alias": "myProcess",
  "api_version": 1,
  "created": "2018-12-19T00:58:26.000Z",
  "current_operation": "nothing",
  "enforcement": true,
  "fid": "9476e38d-096b-4734-9f94-ac568df311ed",
  "job_status": "succeeded",
  "last_error": {},
  "locked": false,
  "next_operation": "update_process",
  "notifications": {
    "drift": "on",
    "enforcement": "on"
  },
  "principal": "root",
  "process_status": "alive",
  "provider": "azure",
  "scheduled": "2018-12-19T01:04:08.000Z",
  "updated": "2018-12-19T01:04:50.219Z",
  "user": "root"
}

Above, the next_operation field now has the value update_process.