---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-service-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Types of configuration data supported by DevOps Config

# Types of configuration data supported by DevOps Config {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

DevOps Config stores configuration data of every layer of the IT stack in
a centralized location.  
Wichtig:  
DevOps Config is now deprecated and no longer supported or available for new activation.  
Configuration data includes:

* App and service configuration
* Middleware configuration (databases, message queues, load balancers, for example)
* Kubernetes and Service Mesh configuration
* Cloud resources configuration (AWS, GGP, Azure DevOps, for example)
* Traditional infra configuration (servers, VMs, network, for example)
{#config-data-devops-config__ul_fbc_vzx_2pb}  

|-|-|-|-|
| API keys | passwords | usernames | feature toggles |
| install paths | load balancing methods | database connections | heap sizes |
| scaling rules | geo regions | host names | IPs |
| cluster settings | sizing | sudo user lists | ssh |
| patching levels | firewalls | URLs | certificates |
| versions | build numbers | hot fixes | -- |
[ ]

{#config-data-devops-config__table_dsh_shd_3pb}

Typically configuration data is stored in files (.json, .yaml, .properties, .ini, .xml, .csv)
and is located in a variety of places, including GIT repos, network folders, third-party tools
(JFrog artifactory, Sonatype Nexus) other databases.

DevOps Config manages and validates your configuration data in a centralized
location as the single source of truth.