Unable to use output secrets in Container Script step
complete
U
Unique Lion
We have a Shell Script Step that sets some output variables as secrets and we are not able to refer it in the same container step.
Log In
Prasad Satam
complete
Thank you for feedback, Closing this Feature Request.
Prasad Satam
Rubber Scallop - Thank you for reviewing the video, I want to mention that it is not a workaround, it is about replacing "Container Step" with "Step Group + Run Step" combination. Run step is an advanced version of Container Step. So, if you are trying to do certain action/function in Container Step today, what we recommend is to use Step Group + Run step instead of Container Step which will be able to evaluate the output secret and use it in the action/function. If needed, we can get on a call. In the mean time, if you can share the pipeline through a support ticket with us cc Reasonable Hamster
Prasad Satam
pending feedback
Hi Unique Lion Exceptional Mole Fawn Antelope
Thanks for your feedback on this feature request! We've reviewed the issue and put together a video walkthrough explaining the problem and a workaround.
🔹 Summary of the video:
Currently, output variables marked as secrets in a Shell Script Step cannot be referenced in a Container Step, causing an error. As a feasible solution, you can use a Step Group with a Run Step, which allows secrets to be shared across steps due to the shared execution context. This method successfully enables secret usage where needed.
🎥 Check out the video here: https://www.loom.com/share/7b427cbec90648549eedc75daf56485a?sid=611b9046-9a2b-4499-b83d-3cb699764f2d
Please take a look at following documentation which has note for recommendation
We’d love for you to take a look and let us know if this approach works for your use case. If you still face challenges, please share your feedback here so we can explore further improvements.
Looking forward to your thoughts!
R
Rubber Scallop
Prasad Satam Hi Prasad, we are also interested in this feature. The work around provided unfortunately won't work for us as this exposes the secret value to users if we add a stepgroup and run step consumes the secret and has to pass it to container step, which is what we want to avoid.
F
Fawn Antelope
This looks more like a bug than a feature request... having the same issue.
E
Exceptional Mole
Is there any update on this?
Prasad Satam
long-term
Thanks for the feedback! This enhancement request has been given top priority and is now officially in our development pipeline!
We will keep you updated on the progress and let you know as soon as it is available.
Should you have any questions, suggestions, or thoughts you'd like to share, please feel free to add more to this feature request.
U
Unique Lion
Support request 54097 has details on this.
Sudarshan Purohit
Hi Unique Lion, could you point us to the place where this is seen, or perhaps a sample to reproduce the behaviour?
Sudarshan Purohit
under review