You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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.
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 returnedWhat 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.
The text was updated successfully, but these errors were encountered: