Skip to content

Instantly share code, notes, and snippets.

@luckymike
Last active August 29, 2015 14:17
Show Gist options
  • Save luckymike/5d26c0f49bf278bb3ddd to your computer and use it in GitHub Desktop.
Save luckymike/5d26c0f49bf278bb3ddd to your computer and use it in GitHub Desktop.
Who, What, Where, Why, When, How of Continuous Provisioning

Continuous Provisioning results in infrastructures that change over time in response to engineering actions. Infrastructure can be represented as a story that develops over time.

Journalism teaches "Who, What, Where, Why, When, How" as the 5 questions to answer in telling a story. We can ask the same questions of our continuously provisioned systems:

  • Who: The engineer whose change(s) triggered the provisioning event.
  • What: The codebase that changed (e.g. git repo), which corresponds to specific provisioned systems.
  • Where: The destination of the provisioned systems. This might be the account/region/provider into which the provisioning occurred, as well as the operating environment (e.g. production, staging) of the provisioned system.
  • Why: The change(s) that trigged the provisioning event.
  • When: A timestamp when the provisioning event occurred.
  • How: The method by which the system(s) were provisioned (e.g. CI system, CLI tooling, web-console).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment