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
Copy file name to clipboardExpand all lines: github-services/aws-opsworks/index.md
+9-2Lines changed: 9 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,6 @@ Try to identify the least number of privileges required to trigger these deploym
29
29
30
30
If you're using [hubot-deploy][10] then you can specify different stacks and applications and group them into an environment. An example `apps.json` script for hubot looks like this.
31
31
32
-
33
32
### apps.json entry
34
33
35
34
```json
@@ -72,7 +71,15 @@ The associated GitHub Deployment API payload ends up looking like this:
72
71
}
73
72
```
74
73
75
-
You can then issue commands like `hubot deploy camo to staging` or `hubot deploy camo/my-topic-branch to production`.
74
+
You can then issue commands like:
75
+
76
+
`hubot deploy camo to staging`
77
+
78
+
or
79
+
80
+
`hubot deploy camo/my-topic-branch to production`.
81
+
82
+
The deployment will still be triggered with the credentials stored on GitHub.
0 commit comments