Skip to content
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.

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

Fixing minor doc issues #6173

Merged
merged 2 commits into from
Dec 5, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions docs/eventing/sinks/integration-sink/aws_s3.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ The `IntegrationSink` supports the Amazon Web Services (AWS) S3 service, through

For connecting to AWS the `IntegrationSink` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:

```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```
```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```

## AWS S3 Sink Example

Expand Down
8 changes: 4 additions & 4 deletions docs/eventing/sinks/integration-sink/aws_sns.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@ The `IntegrationSink` supports the Amazon Web Services (AWS) Simple Notification

For connecting to AWS the `IntegrationSink` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:

```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```
```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```

## AWS SQS Sink Example
## AWS SNS Sink Example

Below is an `IntegrationSink` to send data to AWS SNS:

Expand Down
6 changes: 3 additions & 3 deletions docs/eventing/sinks/integration-sink/aws_sqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ The `IntegrationSink` supports the Amazon Web Services (AWS) Simple Queue Servic

For connecting to AWS the `IntegrationSink` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:

```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```
```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```

## AWS SQS Sink Example

Expand Down
6 changes: 3 additions & 3 deletions docs/eventing/sources/integration-source/aws_ddbstreams.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ The `IntegrationSource` supports the Amazon Web Services (AWS) DynamoDB Streams

For connecting to AWS the `IntegrationSource` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:

```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```
```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```

## AWS DynamoDB Streams Example

Expand Down
6 changes: 3 additions & 3 deletions docs/eventing/sources/integration-source/aws_s3.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ The `IntegrationSource` supports the Amazon Web Services (AWS) S3 service, throu

For connecting to AWS the `IntegrationSource` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:

```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```
```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```

## AWS S3 Source Example

Expand Down
6 changes: 3 additions & 3 deletions docs/eventing/sources/integration-source/aws_sqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ The `IntegrationSource` supports the Amazon Web Services (AWS) Simple Queue Serv

For connecting to AWS the `IntegrationSource` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:

```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```
```bash
kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
```

## AWS SQS Source Example

Expand Down
Loading