> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/user-guide/workspaces/job-output.md).
# Job Output
Each plan and apply step in a job's output has a **Structured** / **Console** toggle. **Console** shows the raw Terraform/OpenTofu CLI output; **Structured** renders the same plan or apply as a resource-by-resource change list.
A plan step with the Structured view selected
### Structured view
Each resource in the structured view shows:
* An **action** badge — `create`, `update`, `delete`, `replace` (destroy + create), `import`, or `no-op`
* The specific attributes changing, with unchanged attributes collapsed by default (expanded by default for imports, since the point of reviewing an import is usually to check what already matches)
* A provider icon next to the resource address
Use the **filter resources by address** search box and the **operation filter** (multi-select, with a count per operation) to narrow a large plan down to the changes you care about.
{% hint style="info" %}
Sensitive values are redacted before they leave the executor, in both Structured and Console views — not just hidden client-side.
{% endhint %}
### Apply-time structured output
During an apply, the structured view updates live, per resource, as Terraform/OpenTofu applies each change — you don't have to wait for the whole apply to finish to see which resources have completed. Once the apply finishes, an **Outputs** section lists the workspace's Terraform outputs, with sensitive outputs redacted the same way as resource attributes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.terrakube.io/user-guide/workspaces/job-output.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
