Skip to content
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

Accessing secrets with op CLI is case insensitive normally, but case sensitive when a connect server is used #73

Open
LP0101 opened this issue Sep 11, 2023 · 0 comments

Comments

@LP0101
Copy link

LP0101 commented Sep 11, 2023

When trying to read a secret with op read, the operation is case insensitive normally, but case sensitive when using a connect server. This disparity in behaviour has lead to confusion where a given secret may work on a developer's machine, but the reference won't work once deployed if a connect server is being used.

@LP0101 LP0101 changed the title Accessing secrets with op is case insensitive normally, but case sensitive when a connect server is used Accessing secrets with op CLI is case insensitive normally, but case sensitive when a connect server is used Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant