👍 Thanks! Going to close this and test and release it on #530

I noticed in testing that this is working well w.r.t the older release images, but not the environment.

In reviewing this patch, I now see that it's copying environment from the current TaskDefinition.

It should be possible to use the Release EnvironmentUrl to get the encrypted release environment from S3, decrypt it and use that for the run.

Ok, Thanks, I'll update this!

Cool. I'm going to leave the existing commits in the release, we can patch on top of them in due time.

I don't think this is working as expected, see below

$ convox run --detach --release RXOBADAUJUR frontend "webpack --progress --config webpack-prod.config.js"
Running `webpack --progress --config webpack-prod.config.jsa` on frontend... OK

$ convox ps
ID            NAME      RELEASE      SIZE  STARTED         COMMAND
f067a1c76125  frontend  RXOBADAUJUR  0     13 seconds ago  sh -c 'webpack --progress --config webpack-prod.config.js'

$ convox exec f067a1c76125 sh
$ /frontend # env
...
RELEASE=RZUUCAXHSZD

Shouldn't the RELEASE variable be the one specified by --release?

Workaround of course is to prefix the command with "RELEASE=RXOBADAUJUR webpack ..."

@snario your expectation is correct around the RELEASE value.

Another patch is needed to correctly pick up the right environment for the specified release.

I do believe this is picking up the right docker images for the specified release. Did your test confirm that?