You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 5, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/guides/creatingatarget.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,15 @@ FIELDS:
59
59
60
60
In addition to be able to interact with AWS you need to have your AWS API keys available. You may specify them in an object manifest but for better security you will want to use a Kubernetes secret.
61
61
62
-
Create the following object by saving the YAML manifest in a file and using the `kubectl apply` command.
62
+
Create a Kubernetes secret called `awscreds` from the command line like so:
Then, create the following object by saving the YAML manifest in a file and using the `kubectl apply` command.
63
71
64
72
```yaml
65
73
apiVersion: targets.triggermesh.io/v1alpha1
@@ -89,7 +97,7 @@ kind: PingSource
89
97
metadata:
90
98
name: ping-lambda
91
99
spec:
92
-
data: '{"hello": "triggermesh"}'
100
+
data: '{"name": "triggermesh"}'
93
101
schedule: '*/1 * * * *'
94
102
sink:
95
103
ref:
@@ -114,7 +122,9 @@ NAME URL READY REASON AGE
114
122
lambda-guide True 3m12s
115
123
```
116
124
117
-
Finally head over to the AWS Lambda console and see the logs of your Lambda. It will show the `{"hello": "triggermesh"}` string in the standard output.
125
+
Finally, go to the AWS Lambda console and see the logs of your Lambda function invocation in a CloudWatch log stream like in the screenshot below:
0 commit comments