iterative / iterative/cml.dev

`runner` OIDC credential management

Open
#391 1 comment 3 reactions 0 assignees View on GitHub
discussion documentation
Dominant language
TypeScript
Stars
13
Forks
22
PR merge metrics
No merged PRs in 30d

Description

- [ ] Document warning about using "short-term" credentials
- [ ] Document/Show possible ways to extend credential life?
- [ ] Document/provide examples for "refreshing" credentials used by the `cml runner` created instance.

Why? By default, these OIDC credentials expire after `1hr` which is likely to be surpassed by ML workflows. After which time cml will fail to self-delete.

----
### Other notes:
on `AWS` code wise the credential format is the exact same and essentially no changes are required
on `GCP` credentials format was different requiring custom parsing to determine the `ProjectID` see: https://github.com/iterative/terraform-provider-iterative/pull/506
on `az`/`azure` 🙈 I have done zero testing

**/CC** https://github.com/iterative/cml.dev/pull/208
Follow up of iterative/cml#862

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.