stikkireddy
stikkireddy
@zsxwing what is the intended entrypoint for the docker image? the various different shell options?
There is no explicit dependency between `databricks_mws_credentials`, `aws_iam_role_policy`. If you print your terraform graph it will probably try to create policy attachment in parallel with `databricks_mws_credentials`. The `databricks_mws_credentials` will fail...
Can you confirm the policy and assume role on aws are created correctly? With the write externalid clause in the assume role/trust relationship and the right policy for the attached...
will have time next week to split up the PR.
I can pick this up next week and ignore the changes
From my understanding the way that defaults applied to "blocks" such as lists and sets require the block to be declared for it to work. As you can see in...
AWS Databricks workspace deployment limits are documented here: https://docs.databricks.com/resources/limits.html#limits
@nfx please close this PR i am submitting another smaller PR. Eng has resolved the drift issue please close this for preference of managing the changes at #1748
@Yard1 any updates on this?
@Yard1 did you happen to test this with tp > 1? IIRC with tp > 1 vllm also calls ray init and does that impact this at all?