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
feat: add support for secrets field in step configuration
Add the `secrets` field to the Step struct, allowing users to specify
Buildkite secrets that should be injected into step environments.
Supports both formats as documented by Buildkite:
- Array format: ["API_ACCESS_TOKEN", "DATABASE_PASSWORD"]
- Map format: {"MY_API_KEY": "API_ACCESS_TOKEN"}
Changes:
- Add Secrets field as interface{} to support both formats
- Add tests for secrets parsing (array and map formats)
- Add tests for secrets in nested steps within groups
- Add pipeline generation tests for both formats
- Add documentation with examples in README.md
Closes#113
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+61Lines changed: 61 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -342,6 +342,67 @@ steps:
342
342
command: "echo deploy-bar"
343
343
```
344
344
345
+
### `secrets` (optional)
346
+
347
+
Add `secrets` to inject [Buildkite Secrets](https://buildkite.com/docs/pipelines/security/secrets/buildkite-secrets) into your command steps. Secrets can be specified in two formats:
348
+
349
+
**Array format** - secret names are used as environment variable names:
0 commit comments