Skip to content

Update Introspection and layouts.md #489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nahumtimerman merged 1 commit into from
Dec 28, 2025
Merged

Update Introspection and layouts.md #489

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/environment-services/Introspection and layouts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@ While infrastructure orchestration using Infrastructure as Code (IaC) framework

> ![Introspection](/img/env-resources.png)

Based on the introspection data, Torque generate __Resource layout__ that is usually used by the environment consumer that is not an expert in IaC of automation frameworks. The layout will highlight the interesting entities out of the large amount of resources that deployed in the environment.
Based on the introspection data, Torque generates a __Resource layout__, which is usually used by an environment consumer (who may not be an expert in IaC of automation frameworks). The layout will highlight the interesting entities out of the large amount of resources that deployed in the environment.

In the following example, we deployed a single Terraform file that deployed a 3 tier wordpress application. The deployment process ended and 28 cloud resources created.

> ![Introspection](/img/env-resources-infra.png)

Out of the 28 deployed resources, Torque highlights the 3 VM with their basic attributes like public IP and instance type presented on the cards. The introspection data, is used to enable resource Actions, workflows and remote connection for specific resource types.

> ![Introspection](/img/env-resources-view.png)
> ![Introspection](/img/env-resources-view.png)
Loading