You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to access a cloud secret when not logged in, I got the following error message: RUN <the command I ran with the secret>: unauthorized
As it's common for a secret to be a password or access token, the user might think unauthorized indicates there is a problem with the password/token, when in fact it's earthly that cannot access the cloud secrets provider to fetch the secret.
Try to access a secret via RUN --secret or RUN --mount=type=secret,id=<SECRET_PATH>,mode=0400,target=/root/.ssh/id_rsa \<your command\>
When logged in: earthly +secret-flag-test and earthly +mounted-secret-test works as expected
When not logged in it fails, e.g.: EARTHLY_TOKEN=fake earthly +secret-flag-test What should have happened?
The error message should be more explicit about not being able to access the secret.
Perhaps if the user is not logged in the error message should state it explicitly
Other Helpful Information
When the user is logged in but the secret is not found - earthly tells the user the secret could not be found
The text was updated successfully, but these errors were encountered:
What went wrong?
While trying to access a cloud secret when not logged in, I got the following error message:
RUN <the command I ran with the secret>: unauthorized
As it's common for a secret to be a password or access token, the user might think
unauthorized
indicates there is a problem with the password/token, when in fact it's earthly that cannot access the cloud secrets provider to fetch the secret.Try to access a secret via
RUN --secret
orRUN --mount=type=secret,id=<SECRET_PATH>,mode=0400,target=/root/.ssh/id_rsa \<your command\>
while not logged in
When logged in:
earthly +secret-flag-test
andearthly +mounted-secret-test
works as expectedWhen not logged in it fails, e.g.:
EARTHLY_TOKEN=fake earthly +secret-flag-test
What should have happened?
The error message should be more explicit about not being able to access the secret.
Perhaps if the user is not logged in the error message should state it explicitly
Other Helpful Information
When the user is logged in but the secret is not found - earthly tells the user the secret could not be found
The text was updated successfully, but these errors were encountered: