# Deployment modes override and rename to override with another type? **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [October 10, 2025, 7:49am UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339 "2025-10-10T07:49:04Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 10, 2025, 7:49am UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/1 "2025-10-10T07:49:04Z")
@paul-griffith I don't know if it's an intended behaviour. I've created 3 modes DB\_MYSQL, DB\_POSTGRES, DB\_SQLSERVER Initially I had 3 connections for various database flavour: - bdref (mysql) - bdref\_postgres (postgres) - bdref\_sqlserver (sqlserver) Initially I think it was not possible to override a connection and change the **driver type**... But, if I create an override on bdref\_postgres and I rename it "bdref" it seems to be ok ? But is it supported ? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0cd7f69b8dc143ccadf2e6807219a81884f69555.png) @Kevin.Herron as for database connection, can we have a device depending from the deployment mode ? device A in one mode is modbus but device A in another mode is Simulator ? (not a modbus with another settings) ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 10, 2025, 7:55am UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/2 "2025-10-10T07:55:45Z")
seems to be supported according the docs: > **[Gateway Deployment Modes | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.3/platform/gateway/web-interface/platform/gateway-deployment-modes)** > > Gateway Deployment Modes allow you to configure different running environments for your Gateway. This can be useful in cases where you want to use your Gateway in different capacities, such as in a production or development environment. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 10, 2025, 4:15pm UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/3 "2025-10-10T16:15:10Z")
Deployment modes can change anything (though it's not necessarily recommended). If it helps, think of it as a single project inheritance tree. If you're in the `dev` mode, you're consuming external -\> system -\> core, then whatever `dev` defines, and then potentially overridden by anything `local`: digraph Tree { rankdir=TB; node [shape=box]; edge []; External; System; Core; Dev; Test; Prod; Local; Actual [label="Loaded Config", style=filled, fillcolor=lightblue]; External -\> System; System -\> Core; Core -\> {Dev, Test, Prod}; Dev -\> Local; Local -\> Actual; } Then if you switch to `test` you're using a totally different set of resources: digraph Tree { rankdir=TB; node [shape=box]; edge []; External; System; Core; Dev; Test; Prod; Local; Actual [label="Loaded Config", style=filled, fillcolor=lightblue]; External -\> System; System -\> Core; Core -\> {Dev, Test, Prod}; Test -\> Local; Local -\> Actual; } And if you started your gateway _without_ a deployment mode, all your modes are ignored: digraph Tree { rankdir=TB; node [shape=box]; edge []; External; System; Core; Dev; Test; Prod; Local; Actual [label="Loaded Config", style=filled, fillcolor=lightblue]; External -\> System; System -\> Core; Core -\> {Dev, Test, Prod}; Core -\> Local; Local -\> Actual; } ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 10, 2025, 4:19pm UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/4 "2025-10-10T16:19:09Z")
Technically supported yes, but not by the UI, which has never supported the idea of changing the "type" of some instance of an extension point once configured (driver type, JDBC driver type, OPC connection, etc...), even before deployment modes existed. ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 10, 2025, 5:11pm UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/5 "2025-10-10T17:11:51Z")
In fact, from the gateway UI, I can obtain different JDBC driver types for each deloyement mode of one named connection. I create one connection "bdref" with Mysql driver. I create another connection "bdref\_postgres" with postgres driver. I create an override for the "bdref\_postgres" connection with a deployement mode set to DB\_POSTGRES I rename the overrided "bdref\_postgres" to "bdref" and then this override is displayed under the "bdref" connection. As a consequence: the connection "bdref" has a connection of another driver type. I was looking to obtain this result frm the gateway UI but I don't known if it's "allowed" from an override point of view. **It seems that for a same ressource name, a different type of ressource is allowed in different deployement mode ?** That's perfect for my need ! But I wonder if I can use this pattern of deployement for db connections, driver or user source ? C:\Program Files\Inductive Automation\Ignition\data\config\resources\core\ignition\database-connection\bdref ```json { "connectURL": "jdbc:mysql://127.0.0.1:3306/bdref", "connectionProps": "zeroDateTimeBehavior\u003dconvertToNull;connectTimeout\u003d120000;socketTimeout\u003d120000;", "connectionResetParams": "", "defaultTransactionLevel": "DEFAULT", "driver": "MySQL ConnectorJ", ... } ``` C:\Program Files\Inductive Automation\Ignition\data\config\resources\DB\_POSTGRES\ignition\database-connection\bdref ```json { "connectURL": "jdbc:postgresql://localhost:5432/bdref", "connectionProps": null, "connectionResetParams": "", "defaultTransactionLevel": "DEFAULT", "driver": "PostgreSQL JDBC Driver", ... } ``` ---
**Author:** ![fry0313](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@fry0313](https://forum.inductiveautomation.com/u/fry0313)\ **Post date:** [October 30, 2025, 4:54am UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/6 "2025-10-30T04:54:11Z")
hey @mazeyrat , did you end up testing this configuration? This is exactly what I’m looking for as well. I want an IdP to be of different types in dev and prod, so I can just change the deployment mode while using the same IdP. For what it’s worth, I interpreted @Kevin.Herron ‘s message as Ignition would support this behaviour. The reason you can’t change the type isn’t related to deployment modes (it was never allowed on an existing config), and since you renamed the overridden "bdref\_postgres" to “bdref“, that “bdref“ will be used if you select DB\_POSTGRES deployment mode, instead of the core resource, since you have that resource now defined in DB\_POSTGRES mode. Being a different “type” should not stop Ignition from using that resource. I haven’t tested this, though, so if you have carried out some real-world tests already, please let us know. ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 30, 2025, 9:17pm UTC](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/7 "2025-10-30T21:17:45Z")
I only tested this approach to change the driver type of a db connection accoding to the deployment mode and it works.