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
After logging in, running infisical secrets set generates a "You must be logged in to run this command. To login, run [infisical login]" error, though infisical secrets get (with a projectId) will return data.
To Reproduce
Steps to reproduce the behavior:
Set INFISICAL_API_URL (export INFISICAL_API_URL=https://<REDACTED_FQDN>/api)
Try to set a secret (infisical secrets set --env=staging TEST_SECRET=test)
Get error message (You must be logged in to run this command. To login, run [infisical login]
Try to get a secret (infisical secrets --projectId <REDACTED_PROJECT_ID> --env=staging get TEST_SECRET)
Get table containing "not found" for the SECRET VALUE (expected, as it is unset). I am able to get a secret set via the web UI for the dev environment.
Expected behavior
I'd expect step 3 to succeed, setting the secret properly, based on the documentation.
Platform you are having the issue on:
CLI
MacOS: infisical version 0.22.2
Alpine (CI container): infisical version 0.22.2
Self-Hosted Docker-Compose Setup
Installed today using :latest.
Additional context
Tested from my workstation and our GitLab CI/CD pipeline.
The machine identity in question has the following permission in the project:
The text was updated successfully, but these errors were encountered:
Describe the bug
After logging in, running
infisical secrets set
generates a "You must be logged in to run this command. To login, run [infisical login]" error, thoughinfisical secrets get
(with a projectId) will return data.To Reproduce
Steps to reproduce the behavior:
export INFISICAL_API_URL=https://<REDACTED_FQDN>/api
)export INFISICAL_TOKEN=$(infisical login --method=universal-auth --client-id=<REDACTED_CLIENT_ID> --client-secret=<REDACTED_CLIENT_SECRET> --silent --plain
)infisical secrets set --env=staging TEST_SECRET=test
)You must be logged in to run this command. To login, run [infisical login]
infisical secrets --projectId <REDACTED_PROJECT_ID> --env=staging get TEST_SECRET
)Expected behavior
I'd expect step 3 to succeed, setting the secret properly, based on the documentation.
Platform you are having the issue on:
CLI
Self-Hosted Docker-Compose Setup
Installed today using
:latest
.Additional context
Tested from my workstation and our GitLab CI/CD pipeline.
The machine identity in question has the following permission in the project:
The text was updated successfully, but these errors were encountered: