Skip to content

Commit 7316912

Browse files
quetzalliwritesquetzalliwrites
authored
docs: adding lineNumber to larger code blocks (#32)
* 1/2 services pages done + capabilities, enterprise, getting started, integrations * more aws services done * more aws services done * finished aws docs * starting snow docs * fixed my dumbass mistake, wrote lineNumbers instead of showLineNumbers * fixing my dumbass mistake in snow docs too, wrote lineNumbers instead of showLineNumbers * finished adding showLineNumbers to snow docs
1 parent 9d86b6e commit 7316912

File tree

123 files changed

+393
-393
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

123 files changed

+393
-393
lines changed

‎src/content/docs/aws/capabilities/chaos-engineering/chaos-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ When active, rules are evaluated sequentially on every request to LocalStack unt
4949

5050
The schema for the configuration is as follows.
5151

52-
```json
52+
```json showshowLineNumbers
5353
[
5454
{
5555
"region": "(str) Region name, e.g. 'ap-south-1'. If omitted, all regions are affected.",

‎src/content/docs/aws/capabilities/config/podman.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ podman machine set --rootful
101101
For the Docker Compose setup, use the following configuration.
102102
When running in rootless mode, ensure to comment out the HTTPS gateway port, as it is unable to bind to privileged ports below 1024.
103103

104-
```yaml
104+
```yaml showshowLineNumbers
105105
services:
106106
localstack:
107107
container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"

‎src/content/docs/aws/capabilities/networking/accessing-endpoint-url.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ docker run --rm -it --dns 172.27.0.2 --network ls <arguments> <image name>
130130
```
131131
</TabItem>
132132
<TabItem label="docker-compose.yml">
133-
```yaml
133+
```yaml showshowLineNumbers
134134
services:
135135
localstack:
136136
container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"
@@ -200,7 +200,7 @@ docker run --rm it --network my-network <image name>
200200
```
201201
</TabItem>
202202
<TabItem label="docker-compose.yml">
203-
```yaml
203+
```yaml showshowLineNumbers
204204
services:
205205
localstack:
206206
# other configuration here

‎src/content/docs/aws/capabilities/networking/external-port-range.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ GATEWAY_LISTEN=0.0.0.0:4766 EXTERNAL_SERVICE_PORTS_START=4710 EXTERNAL_SERVICE_P
5252
```
5353
</TabItem>
5454
<TabItem label="docker-compose">
55-
```yaml
55+
```yaml showshowLineNumbers
5656
services:
5757
localstack-main-1:
5858
container_name: localstack-main-1

‎src/content/docs/aws/capabilities/security-testing/custom-tls-certificates.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ If you run LocalStack in a docker container (which includes using [the CLI](/aws
3434

3535
Create a `Dockerfile` containing the following commands:
3636

37-
```yaml
37+
```yaml showshowLineNumbers
3838
FROM localstack/localstack:latest
3939
# or if using the pro image:
4040
FROM localstack/localstack-pro:latest
@@ -74,7 +74,7 @@ docker run <docker arguments> <image name>
7474
```
7575
</TabItem>
7676
<TabItem label="docker-compose.yml">
77-
```yaml
77+
```yaml showshowLineNumbers
7878
services:
7979
localstack:
8080
image: <image name>

‎src/content/docs/aws/capabilities/security-testing/explainable-iam.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ However we have not included the `iam:PassRole` permission, and we will use the
2828

2929
Create a policy document named `policy_1.json` and add the following content:
3030

31-
```json
31+
```json showshowLineNumbers
3232
{
3333
"Version": "2012-10-17",
3434
"Statement": [
@@ -113,7 +113,7 @@ You can incorporate this action into the policy.
113113
For illustrative purposes, we will keep the example straightforward, using the same wildcard resource.
114114
Edit the `policy_1.json` file to include the `iam:PassRole` action:
115115

116-
```json
116+
```json showshowLineNumbers
117117
{
118118
"Version": "2012-10-17",
119119
"Statement": [

‎src/content/docs/aws/capabilities/security-testing/iam-policy-stream.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ awslocal sns create-topic --name test-topic
5757
In the other tab, the required policy will be generated.
5858
This policy can then be attached to an IAM role, enabling it to create the resource.
5959

60-
```bash
60+
```bash showshowLineNumbers
6161
Attached to identity: "arn:aws:iam::000000000000:root"
6262

6363
Policy:

‎src/content/docs/aws/capabilities/state-management/cloud-pods.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -299,7 +299,7 @@ AUTO_LOAD_POD=foo-pod localstack start
299299
```
300300
</TabItem>
301301
<TabItem label="Docker Compose">
302-
```yaml
302+
```yaml showshowLineNumbers
303303
services:
304304
localstack:
305305
container_name: "localstack-main"
@@ -353,7 +353,7 @@ LocalStack, upon mounting `init-pods.d` to the appropriate location, will sequen
353353

354354
The docker compose file for correctly mounting `init-pods.d` will look like:
355355

356-
```yaml
356+
```yaml showshowLineNumbers
357357
services:
358358
localstack:
359359
container_name: "localstack-main"
@@ -499,7 +499,7 @@ With such a configuration, the `foo-pod` Cloud Pod will be loaded from the `bar-
499499
To properly configure the remote, you need to provide the needed environment variables when starting the LocalStack container.
500500
For instance, a S3 remote needs a `AWS_ACCESS_KEY` and a `AWS_SECRET_ACCESS_KEY`, as follows:
501501

502-
```yaml
502+
```yaml showshowLineNumbers
503503
services:
504504
localstack:
505505
container_name: "localstack-main"

‎src/content/docs/aws/capabilities/state-management/persistence.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ PERSISTENCE=1 localstack start
2828
```
2929
</TabItem>
3030
<TabItem label="Docker Compose">
31-
```yaml
31+
```yaml showshowLineNumbers
3232
image: localstack/localstack-pro
3333
environment:
3434
- LOCALSTACK_AUTH_TOKEN=${LOCALSTACK_AUTH_TOKEN:?}

‎src/content/docs/aws/enterprise/k8s-operator.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ kubectl apply -f https://raw.githubusercontent.com/localstack/localstack-k8s-ope
2222

2323
You can then deploy a LocalStack instance by storing the following file content as `localstack.yml` and applying it against the cluster via `kubectl apply -f localstack.yml`.
2424

25-
```bash
25+
```bash showshowLineNumbers
2626
apiVersion: api.localstack.cloud/v1alpha1
2727
kind: LocalStack
2828
metadata:

0 commit comments

Comments
 (0)