Revision as of 01:31, 15 December 2021 edit GreenC bot (talk \| contribs) Bots 3,056,215 edits Rescued 1 archive link. Wayback Medic 2.5 ← Previous edit		Revision as of 15:34, 27 February 2022 edit undo InternetArchiveBot (talk \| contribs) Bots, Pending changes reviewers 5,686,432 edits Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.8.6) (BrownHairedGirl - 9550 Next edit →
Line 8: ==Overview== Continuous configuration automation is marketed for [[data center]] and application [[configuration management]]. CCA tools use a programmable framework for configuration and orchestration through coding, planning, and incrementally adopting policies.<ref>{{cite web \| url= http://info.easydynamics.com/blog/continuous-integration-infrastructure-as-code \| title= Continuous Integration: Infrastructure as Code in DevOps \| last= Ramos \| first= Martin \| website= easydynamics.com \| date= 4 November 2015 \| access-date= 11 May 2016 \| archive-date= 6 February 2016 \| archive-url= https://web.archive.org/web/20160206165308/http://info.easydynamics.com/blog/continuous-integration-infrastructure-as-code \| url-status= dead }}</ref><ref>{{cite report \|title=Infrastructure As Code: Fueling the Fire for Faster Application Delivery \|publisher=Forrester \|date=March 2015}}</ref> ==Relationship to DevOps==

Continuous configuration automation: Difference between revisions