Skip to content

Cluster creation from the terminal with secret env forwarding #334

@betolink

Description

@betolink

I'm trying to figure out how can something like this work:

coiled batch run --name test
--keep-alive \
--secret-env AWS_ACCESS_KEY_ID=<ID> \
--secret-env AWS_SECRET_ACCESS_KEY=<KEY>  \
--wait-for-ready-cluster  \
--region us-west-2 \
--spot-policy spot_with_fallback \
--max-workers 4 \
echo "ready"

turns out --keep-alive is not a valid arg for batch jobs, and if we use coiled run, there is not a --secret-env arg.
I'm trying to avoid setting up the cluster from a notebook where this is trivial. Maybe I'm missing something?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions