Automate Collaboratively with Infrahub Proposed Changes
Once teams start working to integrate automation into their day to day operations, being able to review and participate in change management becomes essential to success. Proposed changes inside of Infrahub allows teams to fully control when data is merged as well as check it for necessary requirements. Oftentimes, peer reviewing of changes becomes a vital safeguard. This is a default feature of Infrahub.
Infrahub proposed changes allows teams to:
- Verify Changes: Enables a human operator to sign off on a change before it’s ingested into production data repositories.
- Run Business Intelligence Checks: Programmatically check that designs align with configurations catered to business needs
- Enforce Design Validity: Does every leaf need two connections to a spine? Do routing processes need secure configurations? Ensure the right configuration every time.
- Compare Before and After: Analyze impact to artifacts, configurations, files, and more before a change is accepted.
You can read more about how proposed changes in Infrahub can bring higher levels of control and safety to teams and their automation-led efforts in our official documentation. Meanwhile, check out this short video that we created for Autocon2 where we propose and accept a change to a demo system.
