Casper da Costa-Luis
Casper da Costa-Luis
@shcheklein found that there are multiple instances running for about a week. We need: - [ ] automatic warning (email etc.) from AWS if instances run for more than e.g....
also https://github.com/cloud-custodian/cloud-custodian (@dberenbaum suggestion)
There's [`--cloud-permission-set`](https://cml.dev/doc/ref/runner#--cloud-permission-set) and more docs coming soon in https://github.com/iterative/cml.dev/pull/242? EDIT: not relevant; see below.
> CML_TOKEN is misleading do you have a better suggestion?
Don't feel the same. - firstly it's about people users wanting to label things based on their *use* rather than *ownership* (i.e. "I'm using this token for my CML operations,"...
`CML_CI_TOKEN`?
just realised this is also a problem on all runners (not just manual self-hosted) ```yaml jobs: deploy: runs-on: ubuntu-latest steps: - uses: iterative/setup-cml@v1 - uses: actions/checkout@v2 - run: | cml...
potential work-around: use (TP)I `task` (BB Pipelines -> TPI, exporting/forwarding BB env vars -> AWS EC2 -> user script && CML report). ~Likely depends on resolving https://github.com/iterative/terraform-provider-iterative/issues/630.~ moved to https://github.com/iterative/terraform-provider-iterative/issues/633
start of "docs": https://github.com/iterative/terraform-provider-iterative/pull/156 and https://github.com/iterative/terraform-provider-iterative/pull/166
/tests