Codespace secrets not being passed into container #43626
Replies: 4 comments
-
Thanks for bringing it to our notice. We haven't changed anything recently so this should work. Have you followed the directions mentioned in this doc ? - https://docs.github.com/en/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces |
Beta Was this translation helpful? Give feedback.
-
This is not working for me either. (Seems to work fine in actions so I'm rather confused.). I'm sure I'm doing something stupid... Were you able to get it working? What was your fix? |
Beta Was this translation helpful? Give feedback.
-
For anyone having this issue with secrets specifically named |
Beta Was this translation helpful? Give feedback.
-
And is there any docs that describe that codespaces will delete the values of CONTAINER_REGISTRY environment variables? While we now know that is what is going on I still have yet to come across any documentation of this behavior. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
I need to authenticate with an external service (Acquia cloud), and have my key stored in secrets as
ID_RSA
. When I run a codespace, and doecho env
I see all the expected variables relating to my user account, etc., but secret variables do not appear (e.g.,ID_RSA
does not appear as a named variable). I was able to access this secret up until a couple of weeks ago (granted, I didn't look for it via the echo env method while it was working). So, I'm not sure if this is a bug, or if I am unaware of the correct method for accessing a variable to be made available to my container in devcontainer.json.Beta Was this translation helpful? Give feedback.
All reactions