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
Instead of requiring a cluster id to be provided during nutter execution, can job cluster support be added? In our use case, we would only need to supply policy id and not an entire cluster configuration, although if this is implemented it seems like it would make sense to support full-fledge integration with the jobs 2.1 API and creating a job cluster.
Even if the parameter for executing this allowed the cluster configuration to be passed through to the 2.1 api execution, it would be very useful in scenarios where you don't want to have your tests executing on an interactive cluster but instead be run as a job on a job cluster.
If more details are required of this ask please respond back, and I'll try to better articulate my statement above.
The text was updated successfully, but these errors were encountered:
Instead of requiring a cluster id to be provided during nutter execution, can job cluster support be added? In our use case, we would only need to supply policy id and not an entire cluster configuration, although if this is implemented it seems like it would make sense to support full-fledge integration with the jobs 2.1 API and creating a job cluster.
Even if the parameter for executing this allowed the cluster configuration to be passed through to the 2.1 api execution, it would be very useful in scenarios where you don't want to have your tests executing on an interactive cluster but instead be run as a job on a job cluster.
If more details are required of this ask please respond back, and I'll try to better articulate my statement above.
The text was updated successfully, but these errors were encountered: