Closed jakub-bochenski closed 4 years ago
Thanks for this – will need to think about it a bit as it could be breaking change (although unlikely)
Have pushed up a change that removes this mock value (I ended up modifying all runtimes for this).
Let me know if that fixes your situation!
Thanks, I can confirm it works with image sha256:404715798687991ca533c3192d8827c6fafb7659616add63332146dc3764fce4
Set them to blank in case nulls are not allowed. This breaks the default AWS credentials provider. I tried to use profile credentials from ~/aws/.credentials but it's impossible now as the chain picks up those mock defaults instead. Setting the envs to blank in container doesn't help as I see the mock values are still somehow set.