These are chat archives for azukiapp/azk

13th
Apr 2016
Slobodan Mišković
@slobo
Apr 13 2016 16:19

hey folks, I'm experiencing a different behaviour of azk restart -vv --rebuild --reprovision based on whether i supply a system name or not. It seems that some systems don't get rebuilt/reprovisioned unless mentioned by name, perhaps if they are started as dependencies of other systems. Eg:

$ azk restart -vv --rebuild --reprovision
...
azk: ↑ starting `aws-s3` system, 1 new instances...
azk: ✓ checking `azkbuild/566092ff42-proxy:98aa82643a7c835e23bcce9f2926544a83839e21` image...
azk: ◴ waiting for `aws-s3` system to start, trying connection to port http/tcp...
...

vs

$ azk restart -vv --rebuild --reprovision aws-s3
azk: ↓ stopping `aws-s3` system, 1 instances...
azk: ↑ starting `aws-s3` system, 1 new instances...
azk: ✓ checking `jbergknoff/s3rver:latest` image...
azk: ⇲ downloading `jbergknoff/s3rver:latest` image...
azk: ⇲ comparing registry layers and local layers...
azk: ⇲ pulling 6/6 layers.
     [=======                                          ] 17% 1/6
azk: ✓ completed download of `jbergknoff/s3rver:latest`

azk: ↻ provisioning `aws-s3` system...
azk: ◴ waiting for `aws-s3` system to start, trying connection to port http/tcp...
Slobodan Mišković
@slobo
Apr 13 2016 16:25
now, it makes sense to me to not reprovision/rebuild system dependencies when I supply a system name (say, i don't want to have to reprovision the dependent database when rebuilding webserver image), but when not specifying a system name I expect -RB to apply to all the systems. I think I started noticing the 'wrong' behaviour with 0.17 and it's also on 0.18