# Deployment mode tag definition

**URL:** <https://forum.inductiveautomation.com/t/deployment-mode-tag-definition/114125>\
**Category:** Ignition\
**Created:** [February 23, 2026, 2:35pm UTC](https://forum.inductiveautomation.com/t/deployment-mode-tag-definition/114125 "2026-02-23T14:35:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [February 23, 2026, 4:21pm UTC](https://forum.inductiveautomation.com/t/deployment-mode-tag-definition/114125/2 "2026-02-23T16:21:24Z")

</div>

Deployment modes are an _overlay_ on the base resource configuration defined in (generally) the 'core' resource collection:

> [@Deployment modes override and rename to override with another type?](https://forum.inductiveautomation.com/t/deployment-modes-override-and-rename-to-override-with-another-type/111339/3):
>
> 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: Tree External External System System External-\>System Core Core System-\>Core Dev Dev Core-\>Dev Test Test Core-\>Test Prod Prod Core-\>Prod Local Local …

You can copy resources from core to a deployment mode at any time, you'll just have to re-scan your config directory afterwards if you do it while the gateway is running.

But conceptually it's important to only copy the specific paths/resources you actually want to override in the deployment mode, not absolutely everything, or you're giving up most of the benefit of the inheritance cascade.

---

_[View the full topic](https://forum.inductiveautomation.com/t/deployment-mode-tag-definition/114125)._