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

Don't Swallow Error Returns from Paralus #45

Open
estein9825 opened this issue Feb 7, 2023 · 1 comment
Open

Don't Swallow Error Returns from Paralus #45

estein9825 opened this issue Feb 7, 2023 · 1 comment
Labels
enhancement New feature or request new Needs triage

Comments

@estein9825
Copy link

Briefly describe the feature

Before, when Paralus returned an error like "sql: no rows return", it got returned through the CLI. Now, you get a generic error like: could not complete operation create on resource clustertest of type cluster. The real error should be returned

What problem does this feature solve? Please link any relevant documentation or Issues

This prevents a user from knowing why a request failed, which impacts my provider management

(optional) What is your current workaround?

The current workaround is to check the API call directly through postman or debugging inside the library.

@estein9825 estein9825 added enhancement New feature or request new Needs triage labels Feb 7, 2023
@niravparikh05
Copy link
Contributor

@estein9825 trying to understand this a bit more, terraform provider makes api calls to paralus directly, how does returned the underlying error through cli help with your provider management ? Am I missing something here ?

Also using cli if one wants to understand why the command failed, they can make use of --debug flag to introspect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new Needs triage
Projects
None yet
Development

No branches or pull requests

2 participants