Types of configuration data supported by DevOps Config

Release version: Australia

Updated March 12, 2026

1 minute to read

DevOps Config stores configuration data of every layer of the IT stack in a centralized location.

Important:

Starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

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)


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	--

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.