This one was a surprise to me. That the CLI needs to login in order to set a plaintext stack config. If I was setting a secret, I can understand the need for the access token due to the stack using service-managed secrets. Anyway, is that intended behavior of the CLI? To fix this I have now explicitly mapped the access token for the script step since it is a secret. Secret vars need to be explicitly mapped to script steps.
This one was a surprise to me. That the CLI needs to login in order to set a plaintext stack config. If I was setting a secret, I can understand the need for the access token due to the stack using service-managed secrets. Anyway, is that intended behavior of the CLI? To fix this I have now explicitly mapped the access token for the
script
step since it is a secret. Secret vars need to be explicitly mapped toscript
steps.