-
-
Notifications
You must be signed in to change notification settings - Fork 116
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: Add functionality to operate on Workspace Role #447
Comments
/attempt |
Assigned the issue to @Meeran-Tofiq! |
Hello @rajdip-b, I hope you're doing well. Regarding this issue I've had a lot of difficulty in setting up the CLI to make it work for development. First, it said there were issues with it finding Currently, another problem has occurred that I haven't been able to solve: It says index.js doesn't exist in I'm leaving this comment for a few main reasons:
Thank you very much. |
Hey man, we are really sorry about this trouble you faced. I have to admit, it was a very tough job for us to set up multiple package dependency. With the scripts changing in nearly every push, it was even more difficult to manage. But in #451, I have worked on all the fixes. I intend to merge it by tonight. Expect the CLI docs to be updated aswell. Again, sorry about the inconvenience. |
Oh, I see. No worries man you guys are doing an amazing job, don't sweat it. I enjoy working on open-source and I understand these are some issues that come with it. Seriously don't sweat it. Thanks for the kind and timely response as always! :) and looking forward to see the new docs for it XD |
Hey! Gladly, I could make all the updates right away. Please have a read and let me know if you were able to get the CLI up and running following the docs. |
After following the updated docs, I still get the following issue that I don't understand: It says Edited to add the command I wrote: |
Okay, for one, you command is a bit wrong. It will be EDIT: You can join our discord channel to discuss this better imo. |
Okay, I just tried deleting my build folder, and running the command. Seems like it worked. Perhaps, you can try running |
After messing around a bit, I got it working almost. Now it gives a different error: Does this mean I have to install keyshade on my machine even though I have the entire source code on my machine? Also, I'm sorry for not using discord for the discussions, I will from now on use it after I complete this issue. Thanks for your help so far XD |
We didn't know this error still persisted! We put up a fix for it a long back. Anyways, you can just create a |
I tried removing and recreating my fork and set everything up again. It did not work, and still gives the same issue. When I make a fake Thanks. |
I strongly believe it's an issue on our end. Could you just add a {} in your json file? It should solve the issue. Meanwhile, you can also open up an issue regarding the problems you are facing. Someone might pick that up. I myself couldn't get the time to look into the issue. |
Hello. I apologize for the frequent pinging but I have tried a lot to get it to work myself. Now that I've put the empty brackets ( Once again, I apologize for the frequent pinging, I just can't seem to get this to work 😭. If you want to move this conversation to Discord, I will send this message with a more proper explanation of my issue in the collaborators channel on the keyshade Discord. Thanks. |
Hey! We really promote the ask-frequently culture so no worries! Yes, we don't have any way to interact using the UI. All of these interactions are done via Postman. You would need to use this for now. And, there's no pricing involved. The postman API has detailed docs regarding how to get authenticated and make your requests. You would then need to create an API key from API Key Controller. Please reach back to us in case you run into any trouble. |
Thanks, I really appreciate it. Regarding the postman though, I have setup my smtp server correctly and the api even sent me an email correctly. I reset it just in case and reran it to make sure, and it recreated the admin user and everything seems fine. However, when I try to send an OTP email from the postman, I get the following error:
I'd also like to note, that I got the email and it said taht I can sign up now:
But I did not thanks. |
I think if you are logging in as the admin user, you would need to use the password that was provided to you. Ideally you shouldn't use the admin user. If you are logging in using your personal email, use the Send OTP endpoint to send an OTP to your email address. This will automatically create your user. Then you need to Validate OTP. This will send you a jwt token which gets set into your cookies. Next up, you can call the endpoints. You would need to use the Update Self endpoint to set isOnboardjngFinished to true before you do anything though. Hope that helps. |
I finally got it to work! Thank you so much for all your help, now I can finally start development... 😅 A couple of notes regarding why it took me so long though, and I'll be blunt, is that the documentation is not great. Here are a few of my recommendations, which if you find reasonable, I would turn into issues:
I only go the hint that I messed up at that part from your latest comment. Although it is not stated in the
Anyway, I really appreciate all the time it took for all the hand holding I needed. Thank you very much. I will be off now to actually implement the issue at last. Sorry for taking so long XD |
Oh, and one more thing. Should i make new tests for the new commands? thx |
Nah, we haven't implemented CLI testing yet. Just make sure that the commands work as expected and we would be good to go. |
We can definitely improve the
I get the problem, but what I don't get is, where do we add these steps. We would need to add tutorials for these I believe. But then again, things are bound to change real quick. So Im not sure if those tutorials would give long term value or not. |
🎉 This issue has been resolved in version 2.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
We would like to perform the following operations for workspace roles using our CLI:
keyshade workspace role list <workspaceSlug>
)keyshade workspace role get <workspaceRoleSlug>
)keyshade workspace role delete <workspaceRoleSlug>
)keyshade workspace role update <workspaceRoleSlugs> [refer postman for options]
)Solution
role.workspace.ts
undersrc/commands/workspace
command.interface.ts
and name itWorkspaceRoleCommand
workspace.command.ts
src/commands/workspace/role
.workspaceRoleController
underControllerInstance
to make the API calls.The text was updated successfully, but these errors were encountered: