Skip to content

Commit 151cbff

Browse files
committed
2 parents d00b8dd + 50b1e5d commit 151cbff

8 files changed

Lines changed: 50 additions & 17 deletions

File tree

.wordlist.txt

Lines changed: 37 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -530,4 +530,40 @@ txt
530530
Terraform's
531531
TPUs
532532
FPGAs
533-
VPN
533+
VPN
534+
npm
535+
subnets
536+
VPCs
537+
vscode
538+
cpu
539+
CPU
540+
gb
541+
GB
542+
VLANs
543+
RPO
544+
RTO
545+
misconfigurations
546+
Rollout
547+
iac
548+
analytics
549+
quickstart
550+
CloudBees
551+
backoff
552+
jitter
553+
scalable
554+
Scalable
555+
stateful
556+
Customizable
557+
OpenStack
558+
virtualized
559+
Gapped
560+
PodDisruptionBudgets
561+
autoscaler
562+
vCPU
563+
vCPUs
564+
configmaps
565+
replicasets
566+
ClusterRoleBindings
567+
ClusterRoles
568+
CentOS
569+
RHEL

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,3 +15,10 @@ $ npm start
1515
```
1616

1717
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
18+
19+
20+
```
21+
$ npm run build
22+
```
23+
24+
This command starts a local build of the project. When it completes successfully, you can run the built project using "npm run serve". This is good for testing both the build process and the generated production result.

docs/blueprint-designer-guide/blueprints/blueprints-yaml-structure.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -554,7 +554,6 @@ description: ...
554554
metadata:
555555
self-service: true
556556
display-name: "My Custom Blueprint"
557-
icon: "database"
558557
559558
grains: ...
560559
```
@@ -577,15 +576,6 @@ metadata:
577576
display-name: "Production Web Application Stack"
578577
```
579578

580-
#### `icon`
581-
582-
Defines the icon that will be displayed for the blueprint in the Torque catalog. This helps users quickly identify and distinguish between different blueprints.
583-
584-
```yaml
585-
metadata:
586-
icon: "database"
587-
```
588-
589579
## Grains inputs & outputs
590580
Inputs and outputs are used both in the blueprint level and in the grains level. Grains can use inputs and outputs to pass data between IaC components, validate information and eventually lead to reducing the amount of IaC components that needs to be maintained by the organization.
591581

@@ -1280,4 +1270,4 @@ The `visible` property uses Liquid templating syntax to create dynamic condition
12801270

12811271
**Useful Liquid Templating Resources:**
12821272
- [Liquid Templating Introduction](https://shopify.github.io/liquid/basics/introduction/) - Learn the basics and syntax of Liquid templating
1283-
- [Liquid Playground](https://liquidjs.com/playground.html) - Interactive playground to test and experiment with Liquid expressions
1273+
- [Liquid Playground](https://liquidjs.com/playground.html) - Interactive playground to test and experiment with Liquid expressions

docs/eco-system/dev-tools/torque-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ There are two ways to use torque-cli:
2727

2828
To allow the torque-cli to authenticate with Torque, you must provide several parameters:
2929
* *Space*: The Torque space to use
30-
* *Repository*: (Optional) Represents the name of the git repository containing the bleprints and IaC files that will be used when calling Torque
30+
* *Repository*: (Optional) Represents the name of the git repository containing the blueprints and IaC files that will be used when calling Torque
3131
* *Token*: The easiest way to generate a token is via the Torque UI.
3232
1. In your space, go to **Settings > Integrations**.
3333
2. Click **Connect** under any of the CI tools.

docs/environment-services/Introspection and layouts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@ While infrastructure orchestration using Infrastructure as Code (IaC) framework
88

99
> ![Introspection](/img/env-resources.png)
1010
11-
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.
11+
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.
1212

1313
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.
1414

1515
> ![Introspection](/img/env-resources-infra.png)
1616
1717
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.
1818

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

docs/getting-started/getting-started-with-kubernetes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Now, that you have a new space configured, we will associate a repository to the
3434
4. Click on "Connect an Agent"
3535

3636

37-
import pic1 from '/img/getting-repository-ongoarding.gif';
37+
import pic1 from '/img/getting-repository-onboarding.gif';
3838

3939
<img src={pic1} style={{width: 700}} />
4040

docs/getting-started/getting-started-with-terraform.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Now, that you have a new space configured, we will associate a repository to the
3636
3. To __generate a blueprint__ from one of the discovered assets, check the blueprint in the list and click on "Generate Blueprints"
3737
4. Click on "Connect an Agent"
3838

39-
> ![Onboard Repository](/img/getting-repository-ongoarding.gif)
39+
> ![Onboard Repository](/img/getting-repository-onboarding.gif)
4040
4141
## Step #3: Set Quali Agent
4242
In this step, we will configure our newly created blueprint (Created in step #2) to use "Quali Hosted Agent"
File renamed without changes.

0 commit comments

Comments
 (0)