The order of execution of init scripts is:

1. Legacy global (deprecated)
2. Cluster-named (deprecated)
3. Global (new)
4. Cluster-scoped

Arfrenece link that can help is - https://docs.databricks.com/clusters/init-scripts.html#global-init-scripts

You could specify a secret path in an environment at the cluster level

SPARKPASSWORD=<path-value>

and this would be available in global init scripts / cluster-scoped init script

if [[ $SPARKPASSWORD ]]; then
  use $SPARKPASSWORD
fi

I also have this question, and I don't understand the answer from @Sajith Appukuttan​ . This solution would require configuring each new cluster separately with the correct environment variable, correct? That seems like it defeats the purpose of using a global init script. Is there a method that does not require configuration of each new cluster separately?

Hello everyone,

How did you solve this issue? Did you manage to get the secrets through global init script?

Thanks.