Types of configuration data supported by DevOps Config
DevOps Config stores configuration data of every layer of the IT stack in a centralized location.
중요사항:
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)
| 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.