> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/help-faq-and-support/glossary.md).

# Glossary of Terms

Plain-language definitions for InfraGlide product terms. Where the UI label differs from an API or database name, both are noted.

***

### A–C

**Apply**\
Terraform action that creates or updates real cloud resources for a pipeline. Triggered by **Deploy** in the designer.

**Artifact store**\
Object storage used to keep generated pipeline files such as `main.tf.json` and `.terraform.lock.hcl`.

**Canvas**\
The visual Pipeline Designer surface where you place nodes, draw connectors, and arrange containers.

**Component Library**\
Left-hand drawer of drag-and-drop cloud resources for AWS, Azure, or GCP.

**Connection / Connector**\
A visual edge between two nodes. Stored on the pipeline as `connections` and used for validation and Terraform dependency mapping.

**Container node**\
A structural canvas node (VPC, Subnet, Region, and similar) that can enclose child resources and pass inherited attributes.

**Credential**\
Encrypted cloud access material scoped to a Sandbox (AWS keys or Assume Role, GCP service account JSON, Azure service principal).

***

### D–J

**Deployment**\
One execution run (`plan`, `apply`, or `destroy`) recorded for a pipeline, with status, logs, and optional per-resource tracking.

**Destroy**\
Terraform action that tears down resources managed by a pipeline version. Requires typing the confirmation phrase `destroy`.

**Drift**\
Mismatch between saved desired configuration for a managed resource and the live cloud API reading.

**Drift event**\
A stored record of detected drift (`missing`, `added`, or `modified` field changes) for a tracked resource.

**Inherited**\
UI badge on a property that was automatically filled from a parent container or connection rule and is typically read-only while inherited.

**Jane AI**\
InfraGlide’s embedded AI copilot for questions, deployment analysis, security/cost guidance, and canvas assistance.

***

### O–P

**Organization**\
Top-level tenant that owns Workspaces, users, provider policy, and org-wide settings. Resolved from your signed-in identity.

**partial\_success**\
Deployment status meaning some resources progressed before an error. InfraGlide does not auto-rollback.

**Pipeline**\
Saved visual architecture (`components` + `connections`) for one provider inside one Sandbox, including version metadata and Terraform pins.

**Plan / Preview**\
Terraform action that shows proposed changes without applying them. Designer button label: **Preview**.

**Provider pin**\
The cloud provider plugin version stored on a pipeline (for example AWS `5.83.0`) and emitted into `required_providers`.

***

### R–S

**RBAC**\
Role-based access control. Grants attach at organization, Workspace, or Sandbox scope with roles such as Org Admin, Admin, Editor, and Viewer.

**Sandbox**\
Deployable environment inside a Workspace (UI label). API/database name: `project`. Pipelines and credentials always belong to a Sandbox.

**Sync from cloud**\
Drift remediation action that copies live cloud values into the pipeline canvas configuration. Does not write to the cloud by itself.

**Terraform JSON (`main.tf.json`)**\
The single generated configuration file InfraGlide writes for a canvas pipeline before Terraform CLI execution.

**Workspace**\
Top-level team or business-unit area inside an Organization (UI label). API/database name: `folder`. Contains Sandboxes.

***

### Status Words You Will See

| Status                  | Typical meaning                                       |
| ----------------------- | ----------------------------------------------------- |
| `draft`                 | Pipeline not successfully deployed (or newly created) |
| `pending` / `running`   | Deployment accepted or in progress                    |
| `planned`               | Preview (`plan`) finished successfully                |
| `success`               | Apply finished successfully                           |
| `partial_success`       | Apply created some resources then errored             |
| `failed`                | Execution failed                                      |
| `destroyed`             | Destroy finished successfully                         |
| `open` / `acknowledged` | Drift event lifecycle states                          |

***

### See also

* [Core Concepts & Terminology](/getting-started/core-concepts.md)
* [Frequently Asked Questions (FAQ)](/help-faq-and-support/faq.md)
* [Real-Time Drift Detection Overview](/cloud-sync-and-drift-detection/overview.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/help-faq-and-support/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.