@dominicm I found the problem. It’s a bug in the tfjson code. Logged an issue. https://github.com/juxt/roll/issues/11
is it possible to pass parameters to mach? I didn't find that in de docs
the use case is passing the environment such that you can select the right profile from aero
@stijn you can pass in a constants parameter
Pro tip for all: mach --help works
I should generate bash completion
thanks @dominicm
hmmm, I can't figure out what the syntax of mach/constants is (in the Machfile)
mach/constants [environment "staging"]
doesn't seem to work
mach/constants {environment "staging"}
neither
in both cases it says WARNING: Use of undeclared Var cljs.user/environment
ok, you have to use #ref [mach/constant environment]
, but that doesn't work yet in mach/props
@dominicm I think this is a limitation on the usage of constants, no?
mach/constants {environment "staging"}
used to work
yes, but how do I read the value in mach/props
?
Tbh props and constants are two people doing the same thing and giving it a different name
ok, so what is needed is a --property option on the command line 🙂
@dominicm @jonpither now that I have a reliable deploy working, I have 2 questions. I’ll raise them here now to start the conversation but I suspect there’s no quick answer
1/ the only repeatable way to tf apply
is to tf destroy
before doing so. without that I consistently get an error about the ALB already being in use. Should this work or what is the plan for this use case. I need this for my CI/Staging deploy. Using destroy before is fine for this use case but I suspect that’s not intended behaviour.
2/ I can’t see how Blue/Green is achieved with Roll. I will need this for my prod deploys. Can you give me a bit of insight into the vision for this? Or (better) add some text to the README?
BTW: my SSL service is working beautifully now. very happy with that progress