-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI Login and Set Process Does Not Work Per Documentation #1802
Comments
Team has indicated that there is, in fact, an issue with Infisical via Slack. |
Turns out that this just isn't a supported operation. Documentation should be fixed to indicate this or, better yet, implement this. |
Hey @seancallaway . This should be resolved by this week or coming week. Our team is prioritizing this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: