-
Notifications
You must be signed in to change notification settings - Fork 384
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
Added databricks_recipient
resource for Delta Sharing
#1571
Added databricks_recipient
resource for Delta Sharing
#1571
Conversation
do we always need to include ip_access_list {
allowed_ip_addresses = ["0.0.0.0/0"]
} ? |
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.
Suggested a resource rename and left comments about example expansion. Can you also add an acceptance test? e.g. assume that metastore will be provided as TEST_DATABRICKS_METASTORE_ID
environment variable in the testing environment.
docs/resources/recipient.md
Outdated
name = "db2open-recipient" | ||
comment = "made by terraform" | ||
authentication_type = "TOKEN" | ||
sharing_code = "my code " |
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.
please add tune this example with random_password
resource
docs/resources/recipient.md
Outdated
} | ||
|
||
resource "databricks_recipient" "db2db" { | ||
name = "sri-terraform-test-db2db-recipient" |
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.
- make two separate examples (db2open & db2db) explaining what they do in one sentence.
- please use
databricks_current_user
resource instead of names.
docs/resources/recipient.md
Outdated
name = "sri-terraform-test-db2db-recipient" | ||
comment = "made by terraform" | ||
authentication_type = "DATABRICKS" | ||
data_recipient_global_metastore_id = "<cloud>:<region>:<guid>" |
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.
can you expand the example with databricks_metastore
resource to refer the ID from it?
docs/resources/recipient.md
Outdated
|
||
The following resources are used in the same context: | ||
|
||
* [databricks_table](../data-sources/tables.md) data to list tables within Unity Catalog. |
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.
can you add those in the later PRs? :)
AFAIK you don't @alexott it was just a poor example on my part. Ill change it to some other random public ip |
catalog/resource_recipient.go
Outdated
Recipients []RecipientInfo `json:"recipients"` | ||
} | ||
|
||
//func (a RecipientsAPI) list() (recipients Recipients, err error) { |
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.
please remove commented code. we have a generated SDK for that already.
@stikkireddy i think it's better to remove |
docs/resources/recipient.md
Outdated
special = true | ||
} | ||
|
||
data databricks_current_user "current" {} |
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.
data databricks_current_user "current" {} | |
data "databricks_current_user" "current" {} |
docs/resources/recipient.md
Outdated
global metastore usually the format: `<cloud>:<region>:<guid>` | ||
|
||
```hcl | ||
data databricks_current_user "current" {} |
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.
data databricks_current_user "current" {} | |
data "databricks_current_user" "current" {} |
docs/resources/recipient.md
Outdated
|
||
Setting `authentication_type` type to `DATABRICKS` allows you to automatically create a provider for a recipient who | ||
is using Databricks. To do this they would need to provide the global metastore id that you will be sharing with. The | ||
global metastore usually the format: `<cloud>:<region>:<guid>` |
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.
usually the format
this reads strange
Head branch was pushed to by a user without write access
…tabricks into delta-sharing/recipient-resource
databricks_recipient
resource for Delta Sharing
Examples: