php - How Are OpsWorks' Built-In Recipes Versioned? -
when set stack in opsworks, lock in current built-in cookbooks version or use up-to-date version each time lifecycle event triggered?
for custom cookbooks, understand opsworks caches provided recipes when provided rather fetching newest version each time, wonder if same true built-in cookbooks.
i'm concerned few reasons. if cookbooks updated install different version of apache or php or vary default configuration? if setup new instance in layer in old recipe used , end multiple servers different configurations?
also there doesn't appear way customize php5 version gets installed, @ mercy of ubuntu package managers' decision use latest stable version?
i want continue using latest , greatest software versions, deploy them on own time after have been able test application works in new version.
when set stack in opsworks, lock in current built-in cookbooks version or use up-to-date version each time lifecycle event triggered?
when provision new machine, built in cookbook + custom cookbooks requested onto server @ same time. gets updated custom cookbook update requested. why recommendation not copy entire aws cookbook custom cookbook. things modifying can benefit standard community cookbook updates.
i'm concerned few reasons. if cookbooks updated install different version of apache or php or vary default configuration? if setup new instance in layer in old recipe used , end multiple servers different configurations?
this not bane, benefit too. depends on how perceive this. maybe performance improvement can done, , introduction of bugs. needs kept in sync operations people.
you can override parts of built in cookbook placing duplicates ( or customised ) versions in same place in cookbook. converge option
or more complex sure way :
- implement custom recipe cookbook.
- import opsworks cookbooks submodule folder inside cookbooks folder.
- symlink cookbook need version controled main folder now
- evaluate , update needed specific ones
ie :
cd cookbook git submodule add https://github.com/aws/opsworks-cookbooks external-cookbooks/opsworks-cookbooks ln -s external-cookbooks/opsworks-cookbooks/rails rails
this way can update , keep version control of infrastructure code. make , evaluate changes , import changes after you've
i still recommend using converge mode minor changes require hardcoded. mean less duplication , , benefit updates maybe in community version of cookbooks.
if you're using cookbook uses ubuntu way install php - mercy in repo. if using 1 custom compiled version, can compile specific versions. may have either write own or find 1 build , let specify version via attribute on cookbook.
Comments
Post a Comment