-
Notifications
You must be signed in to change notification settings - Fork 1
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
Endpoint, Token, Cert Path, and Cert Key Storage for CLI Tool #2
Comments
/bounty $200 |
💎 $200 bounty • Permify.coSteps to solve:
Don't wait to be assigned. A reward will be given for the best PR. Thank you for contributing to Permify/permify-cli! Add a bounty • Share on socials
|
/attempt #2 |
@Pavan-Nambi: The Permify.co team prefers to assign a single contributor to the issue rather than let anyone attempt it right away. We recommend waiting for a confirmation from a member before getting started. |
hey @tolgaOzen can i work on this? |
@Pavan-Nambi, I have assigned this issue to you. Happy hacking 🚀 |
hey @tolgaOzen , I am bit new to codebase but by storage u mean to store them in some env/yml files? or something else? we retrive from something like this config file?? or some vaults? |
Hello @Pavan-Nambi, by storage I mean a way to prevent users from having to repeatedly enter their credentials when connecting to the Permify API. For this, you can use the path |
got it, thanks |
@tolgaOzen i've made a pr #8 based on what i understood lmk if i did anything wrong, or if u want me to change anything |
Hey @tolgaOzen can i work on this one? |
/attempt #2 |
Putting myself on the queue for collab or in case this needs to be reassigned ✋ |
1 similar comment
Putting myself on the queue for collab or in case this needs to be reassigned ✋ |
Since the issue is not assigned to anyone, I would like to give it a shot or would be happy to collab if possible. Options |
Hello @tolgaOzen, it doesn't look like anyone is assigned this task. I am interested in working on this, could you assign me this task? |
/attempt #2 Options |
Greetings @tolgaOzen, could you please assign this to me? |
/attempt #2 Options |
@tolgaOzen I can see that since this was created a config file has been implemented to store the endpoint, Do we just need to follow the same process for the token + cert, or is this not needed anymore? |
@tolgaOzen, is this issue still open to work? |
Description
We need to implement a feature for storing the endpoint, token, cert path, and cert key in the CLI tool. These credentials should be retrievable from the storage for later use during the client creation process.
Location
permify-cli/internal/client/client.go
Proposed Change
Modify the
New
function inclient.go
to retrieve stored credentials. The updated function could look something like this:Additional Notes
Ensure that the credential retrieval process is secure and efficient.
Include error handling for cases where credentials are missing or incorrect.
The text was updated successfully, but these errors were encountered: