-
Notifications
You must be signed in to change notification settings - Fork 401
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
Add more readability for errors #129
Conversation
nfx
commented
Jun 19, 2020
•
edited
Loading
edited
- Add resource wait retry for workspace create
- Made vscode integration testing simpler
- added read support for username/password for config files
- Made errors concise and explainable
Codecov Report
@@ Coverage Diff @@
## master #129 +/- ##
==========================================
+ Coverage 48.02% 48.24% +0.21%
==========================================
Files 58 58
Lines 7219 7245 +26
==========================================
+ Hits 3467 3495 +28
+ Misses 3690 3681 -9
- Partials 62 69 +7
|
…databricks into fixes
… or check the error message to verify resource is missing; added travis buddy integration; added unit test for handling errors; deprecated dbfs file sync; doc fix for scim user;
… set so it runs with both aws and azure integration tests
…aform-provider-databricks into fixes � Conflicts: � databricks/azure_auth.go
…aware of expiry time of token as metadata; added getAndAssetEnv for generating the dbapi client for testing missing errors
Hey @nfx, TravisBuddy Request Identifier: 155e26f0-b68c-11ea-aaf6-456b40a357ff |
Hey @nfx, TravisBuddy Request Identifier: 9fac8190-b690-11ea-aaf6-456b40a357ff |
@@ -6,59 +6,73 @@ description: |- | |||
Terraform provider databricks. | |||
--- | |||
|
|||
# Databricks Provider |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nfx Headers should align to the common naming convention provided by Hashicorp which are the conventions that the other official providers follow. Guide can be found here: https://www.terraform.io/docs/registry/providers/docs.html#headers. I am reverting it to follow that guide and examples can be found here:
Old Site:
- https://www.terraform.io/docs/providers/aws/index.html
- https://www.terraform.io/docs/providers/azurerm/index.html
New Registry Docs:
- https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication
- https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs
This gives the user similar experience when using the docs.
We should try to use the main headers as it is used to determine the nav on the registry on the right hand side of the page. All H2 or "##" show up on that nav bar so too many makes it confusing. I am going to follow the pattern on the AWS provider as it is very simple nav and you can generate links to specific areas if we need to send links for the H3 blocks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
---
in the beginning of the file is equal to H1, just in case, but comment noted
Hey @nfx, TravisBuddy Request Identifier: 3783c4b0-b69b-11ea-aaf6-456b40a357ff |
Hey @nfx, TravisBuddy Request Identifier: 594857b0-b69f-11ea-aaf6-456b40a357ff |
Hey @nfx, TravisBuddy Request Identifier: a4519a70-b6a2-11ea-aaf6-456b40a357ff |