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

chore: Reference IDs of share objects in share.go error messages. #2270

Merged
merged 2 commits into from
Dec 19, 2023

Conversation

originalrkk
Copy link
Contributor

Without this, we get error messages like

Error: error reading share err = [errors.go:17] object does not exist or not authorized

that are nearly impossible to debug.

Test Plan

This PR only adds extra information to error messages.

Without this, we get error messages like
```
Error: error reading share err = [errors.go:17] object does not exist or not authorized
```
that are nearly impossible to debug.
@sfc-gh-asawicki
Copy link
Collaborator

Hey @originalrkk. Thanks for the PR.

For me, it's fine to add such additional info. Out of curiosity: did you try running the provider with TF_LOG set to DEBUG or TRACE? You get a lot more info that way.

@sfc-gh-asawicki sfc-gh-asawicki changed the title Reference IDs of share objects in share.go error messages. chore: Reference IDs of share objects in share.go error messages. Dec 15, 2023
@originalrkk
Copy link
Contributor Author

Ah, d'oh, good idea. Still think it's useful to have these since ideally we'd only have to fall back to debug for the most pathological / confusing cases.

@sfc-gh-asawicki
Copy link
Collaborator

/ok-to-test sha=514200e8112e8b93a412fe46ede61cefc59c6c62

Copy link

Integration tests failure for 514200e8112e8b93a412fe46ede61cefc59c6c62

@sfc-gh-asawicki sfc-gh-asawicki merged commit b19fe8b into Snowflake-Labs:main Dec 19, 2023
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants