cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Disable ability to choose PHOTON

noorbasha534
Contributor III

Dear all,

as an administrator, I want to restrict developers from choosing 'photon' option in job clusters. I see this in the job definition when they choose it -

"runtime_engine": "PHOTON"

How can I pass this as input in the policy and restrict developers from using photon...

Thank you for the guidance..

Br,

Noor.

1 ACCEPTED SOLUTION

Accepted Solutions

Isi
Contributor III

Hey @noorbasha534 

Did it work?  Consider mark my answer as solution to future users 🙂

Thanks,
Isi

View solution in original post

4 REPLIES 4

Isi
Contributor III

Hi @noorbasha534 ,

To restrict developers from selecting Photon in job clusters, you need to define a cluster policy that enforces constraints on the "runtime_engine" field.

{
  "runtime_engine": {
    "type": "fixed",
    "value": "STANDARD",
    "hidden": true
  }
}

 

•The "type": "fixed" ensures that users cannot modify this value.
• The "value": "STANDARD" forces clusters to only use the Standard runtime, effectively blocking Photon.
•The "hidden": true prevents developers from even seeing this option in the UI.

“I created a new policy called ‘test’ to verify the restrictions, and as you can see, the option doesn’t appear in the menu! 🙂 “ (Without hidden It will appear but you cant select it)

Captura de pantalla 2025-03-18 a las 14.46.36.png
Hope this helps 🙂

Isi

noorbasha534
Contributor III

ah nice...i will try on my side. thanks much.

Isi
Contributor III

Hey @noorbasha534 

Did it work?  Consider mark my answer as solution to future users 🙂

Thanks,
Isi

mnorland
Contributor

You also need to make sure the policy permissions are set up properly. You can/should fix preexisting compute affected by the policy with the wizard in the policy edit screen.

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now