"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "website/docs/internals/machine-readable-ui.html.md" between
terraform-1.0.2.tar.gz and terraform-1.0.3.tar.gz

About: Terraform is a tool for building, changing, and versioning a datacenter infrastructure (written in Go).

machine-readable-ui.html.md  (terraform-1.0.2):machine-readable-ui.html.md  (terraform-1.0.3)
skipping to change at line 57 skipping to change at line 57
The following message types are supported: The following message types are supported:
### Generic Messages ### Generic Messages
- `version`: information about the Terraform version and the version of the sche ma used for the following messages - `version`: information about the Terraform version and the version of the sche ma used for the following messages
- `log`: unstructured human-readable log lines - `log`: unstructured human-readable log lines
- `diagnostic`: diagnostic warning or error messages; [see the `terraform valida te` docs for more details on the format](/docs/cli/commands/validate.html#json) - `diagnostic`: diagnostic warning or error messages; [see the `terraform valida te` docs for more details on the format](/docs/cli/commands/validate.html#json)
### Operation Results ### Operation Results
- `resource_drift`: describes a detected change to a single resource made outsid e of Terraform
- `planned_change`: describes a planned change to a single resource - `planned_change`: describes a planned change to a single resource
- `change_summary`: summary of all planned or applied changes - `change_summary`: summary of all planned or applied changes
- `outputs`: list of all root module outputs - `outputs`: list of all root module outputs
### Resource Progress ### Resource Progress
- `apply_start`, `apply_progress`, `apply_complete`, `apply_errored`: sequence o f messages indicating progress of a single resource through apply - `apply_start`, `apply_progress`, `apply_complete`, `apply_errored`: sequence o f messages indicating progress of a single resource through apply
- `provision_start`, `provision_progress`, `provision_complete`, `provision_erro red`: sequence of messages indicating progress of a single provisioner step - `provision_start`, `provision_progress`, `provision_complete`, `provision_erro red`: sequence of messages indicating progress of a single provisioner step
- `refresh_start`, `refresh_complete`: sequence of messages indicating progress of a single resource through refresh - `refresh_start`, `refresh_complete`: sequence of messages indicating progress of a single resource through refresh
skipping to change at line 88 skipping to change at line 89
"@level": "info", "@level": "info",
"@message": "Terraform 0.15.4", "@message": "Terraform 0.15.4",
"@module": "terraform.ui", "@module": "terraform.ui",
"@timestamp": "2021-05-25T13:32:41.275359-04:00", "@timestamp": "2021-05-25T13:32:41.275359-04:00",
"terraform": "0.15.4", "terraform": "0.15.4",
"type": "version", "type": "version",
"ui": "0.1.0" "ui": "0.1.0"
} }
``` ```
## Resource Drift
If drift is detected during planning, Terraform will emit a `resource_drift` mes
sage for each resource which has changed outside of Terraform. This message has
an embedded `change` object with the following keys:
- `resource`: object describing the address of the resource to be changed; see [
resource object](#resource-object) below for details
- `action`: the action planned to be taken for the resource. Values: `update`, `
delete`.
This message does not include details about the exact changes which caused the c
hange to be planned. That information is available in [the JSON plan output](./j
son-format.html).
### Example
```json
{
"@level": "info",
"@message": "random_pet.animal: Drift detected (update)",
"@module": "terraform.ui",
"@timestamp": "2021-05-25T13:32:41.705503-04:00",
"change": {
"resource": {
"addr": "random_pet.animal",
"module": "",
"resource": "random_pet.animal",
"implied_provider": "random",
"resource_type": "random_pet",
"resource_name": "animal",
"resource_key": null
},
"action": "update"
},
"type": "resource_drift"
}
```
## Planned Change ## Planned Change
At the end of a plan or before an apply, Terraform will emit a `planned_change` message for each resource which has changes to apply. This message has an embedd ed `change` object with the following keys: At the end of a plan or before an apply, Terraform will emit a `planned_change` message for each resource which has changes to apply. This message has an embedd ed `change` object with the following keys:
- `resource`: object describing the address of the resource to be changed; see [ resource object](#resource-object) below for details - `resource`: object describing the address of the resource to be changed; see [ resource object](#resource-object) below for details
- `action`: the action planned to be taken for the resource. Values: `noop`, `cr eate`, `read`, `update`, `replace`, `delete`. - `action`: the action planned to be taken for the resource. Values: `noop`, `cr eate`, `read`, `update`, `replace`, `delete`.
- `reason`: an optional reason for the change, currently only used when the acti on is `replace`. Values: - `reason`: an optional reason for the change, currently only used when the acti on is `replace`. Values:
- `tainted`: resource was marked as tainted - `tainted`: resource was marked as tainted
- `requested`: user requested that the resource be replaced, for example via the `-replace` plan flag - `requested`: user requested that the resource be replaced, for example via the `-replace` plan flag
- `cannot_update`: changes to configuration force the resource to be deleted and created rather than updated - `cannot_update`: changes to configuration force the resource to be deleted and created rather than updated
 End of changes. 2 change blocks. 
0 lines changed or deleted 40 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)