-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix alert show in cli mode without accesskey (close #536) #588
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
Conversation
|
Review app available at: https://hge-ci-pull-588.herokuapp.com |
|
@n1arash Thanks for the PR. There are multiple problems associated with this.
I think for now it will be useful if we show valuable information in the alert box by decoding the For example: If the Please let me know what you think. |
|
do you mean when server is configured but cli is without key we should show the alert right? |
|
Yes instead of showing the response object itself we can provide a message on how to solve the problem? |
|
@karthikvt26 yeah i agree with that i will commit changes ASAP |
|
i added some changes so is this what we are looking for ? |
|
Review app available at: https://hge-ci-pull-588.herokuapp.com |
|
Review app available at: https://hge-ci-pull-588.herokuapp.com |
|
Review app https://hge-ci-pull-588.herokuapp.com is deleted |
<!-- Thank you for submitting this PR! :) --> ## Description Following `metadata-resolve` and `schema` crates, this splits out `execute`, the largest folder in `engine`. Undoubtedly this could be split further. Functional no-op. V3_GIT_ORIGIN_REV_ID: c272908153f78212d1f5dd58819707ac3cbcd439
Description
now make sure that only if accessKey is exist show alert box
What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
Solution and Design
Type
Checklist: