Config-modules is a library that can be utilized by services written in python to run compliance checks (audit and remediation) for multiple products.
- Consistent Interface: Config-modules design helps achieve a consistent interface to invoke compliance workflows, no matter the differences in product level implementation.
- Simplified Implementation: Using a schema based approach helps achieve a simplified controller implementation. Schema serves as the contract between the customer input and the controller logic.
- Future-proof integration: The config module design enables products to catch up any missing APIs without disrupting existing upstream implementations. For example, VC Profile API is under development, we are working with respective product owners to close the gap in future versions.
- Adaptability: The config module is highly reusable across various automation integrations, offering versatility in different deployment scenarios.
- Independent development and Testing: Config module design enables controller owners to independently develop and test product specific drift and remediation.
- Seamless SaltStack Integration: Leveraging the strengths of SaltStack, config-modules seamlessly integrates as a library for Salt extensions, enhancing exisitng workflowless.
|--config_modules_vmware
| |--controllers <---- logic for controllers
| | |--vcenter
| | |--sddc_manager
| | |--....
| |--framework <---- framework related classes
| | |--auth
| | | |--contexts <---- product specific context
| | |--clients <---- product specific client connections
| | |--models <---- model class folder
| | |--utils <---- utils
| |--interfaces <---- user interfaces and APIs to call.
| |--schemas <---- schemas and related utility functions
| |--services <---- service classes (mapper, operations, etc)
| |--tests <---- unit test folder
|--functional_tests <---- functional test folder
|--docs <---- useful documentation
|--devops <---- scripts for CI/CD
