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

Feature/update doc #1332

Merged
merged 13 commits into from
May 26, 2022
Merged

Feature/update doc #1332

merged 13 commits into from
May 26, 2022

Conversation

nkvuong
Copy link
Contributor

@nkvuong nkvuong commented May 24, 2022

  • Upgrade AWS provider for AWS guides
  • Add examples for account-level identities

@codecov
Copy link

codecov bot commented May 24, 2022

Codecov Report

Merging #1332 (3439c66) into master (d014779) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1332   +/-   ##
=======================================
  Coverage   90.60%   90.60%           
=======================================
  Files         118      118           
  Lines       10004    10004           
=======================================
  Hits         9064     9064           
  Misses        559      559           
  Partials      381      381           

docs/guides/unity-catalog.md Outdated Show resolved Hide resolved
docs/guides/unity-catalog.md Outdated Show resolved Hide resolved
Directly manage [Service Principals](https://docs.databricks.com/administration-guide/users-groups/service-principals.html) that could be added to [databricks_group](group.md) within workspace.
Directly manage [Service Principals](https://docs.databricks.com/administration-guide/users-groups/service-principals.html) that could be added to [databricks_group](group.md) in Databricks workspace or account.

To create service principals in the Databricks account, the provider must be configured with `host = "https://accounts.azuredatabricks.net"` on AWS deployments or `host = "https://accounts.azuredatabricks.net"` and `auth_type = "azure-cli"` on Azure deployments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it really available for User Principals only? Is it the same SPN OBO flow issue? :(

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sp can be added to the account as well

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so why do we need auth_type = "azure-cli" then?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤦 - corrected it to AAD tokens

Copy link
Contributor

@nfx nfx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few last changes required

This resource allows you to manage [groups in Databricks Workspace](https://docs.databricks.com/administration-guide/users-groups/groups.html) or [Account Console](https://accounts.cloud.databricks.com/) (for AWS deployments). You can also [associate](group_member.md) Databricks users and [service principals](service_principal.md) to groups. This is useful if you are using an application to sync users & groups with SCIM API.
This resource allows you to manage [groups in Databricks Workspace](https://docs.databricks.com/administration-guide/users-groups/groups.html), [Databricks Account Console](https://accounts.cloud.databricks.com/) or [Azure Databricks Account Console](https://accounts.azuredatabricks.net). You can also [associate](group_member.md) Databricks users and [service principals](service_principal.md) to groups. This is useful if you are using an application to sync users & groups with SCIM API.

To create groups in the Databricks account, the provider must be configured with `host = "https://accounts.azuredatabricks.net"` on AWS deployments or `host = "https://accounts.azuredatabricks.net"` and authenticate using AAD tokens on Azure deployments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Azure Databricks in both cases? :-)

docs/resources/group_member.md Outdated Show resolved Hide resolved
This resource allows you to attach [users](user.md) and [groups](group.md) as group members.
This resource allows you to attach [users](user.md), [service_principal](service_principal.md) and [groups](group.md) as group members.

To attach members to groups in the Databricks account, the provider must be configured with `host = "https://accounts.azuredatabricks.net"` on AWS deployments or `host = "https://accounts.azuredatabricks.net"` and authenticate using AAD tokens on Azure deployments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Azure Databricks in both cases?

Directly manage [Service Principals](https://docs.databricks.com/administration-guide/users-groups/service-principals.html) that could be added to [databricks_group](group.md) within workspace.
Directly manage [Service Principals](https://docs.databricks.com/administration-guide/users-groups/service-principals.html) that could be added to [databricks_group](group.md) in Databricks workspace or account.

To create service principals in the Databricks account, the provider must be configured with `host = "https://accounts.azuredatabricks.net"` on AWS deployments or `host = "https://accounts.azuredatabricks.net"` and authenticate using AAD tokens on Azure deployments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both azure?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ctrl+c, ctrl+v error

This resource is used to [manage users](https://docs.databricks.com/administration-guide/users-groups/users.html), that could be added to [databricks_group](group.md) within the workspace. Upon user creation the user will receive a password reset email. You can also get information about caller identity using [databricks_current_user](../data-sources/current_user.md) data source.
This resource allows you to manage [users in Databricks Workspace](https://docs.databricks.com/administration-guide/users-groups/users.html), [Databricks Account Console](https://accounts.cloud.databricks.com/) or [Azure Databricks Account Console](https://accounts.azuredatabricks.net). You can also [associate](group_member.md) Databricks users to [databricks_group](group.md). Upon user creation the user will receive a password reset email. You can also get information about caller identity using [databricks_current_user](../data-sources/current_user.md) data source.

To create users in the Databricks account, the provider must be configured with `host = "https://accounts.azuredatabricks.net"` on AWS deployments or `host = "https://accounts.azuredatabricks.net"` and authenticate using AAD tokens on Azure deployments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both azure?)

Copy link
Contributor

@nfx nfx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@nfx nfx merged commit 486cb1f into databricks:master May 26, 2022
nfx added a commit that referenced this pull request May 30, 2022
## 0.5.9

* Added warning section for debug mode ([#1325](#1325)).
* Added ability to specify tags for `databricks_job` ([#1337](#1337)).
* Upgraded AWS provider for AWS guides. Added examples for account-level identities ([#1332](#1332)).
* Updated docs to use `application_id` as privilege for `databricks_service_principal` ([#1336](#1336)).
* Added `databricks_service_principal_role` resource ([#1340](#1340)).
* Fixed itegration testing image ([#1342](#1342), [#1343](#1343)).
* Added `skip_validation` for `databricks_external_location` ([#1330](#1330)).
* Added `alert_on_last_attempt` to `databricks_job` ([#1341](#1341)).
* Skip `make test` on doc-only changes ([#1339](#1339)).
* Improve common package test coverage ([#1344](#1344)).
* Re-create purged cluster for `databricks_mount` for AWS S3 ([#1345](#1345)).

Updated dependency versions:

* Bump google.golang.org/api from 0.79.0 to 0.80.0
* Bump github.com/Azure/go-autorest/autorest/adal from 0.9.19 to 0.9.20
@nfx nfx mentioned this pull request May 30, 2022
@nkvuong nkvuong deleted the feature/update-doc branch June 10, 2022 16:19
michael-berk pushed a commit to michael-berk/terraform-provider-databricks that referenced this pull request Feb 15, 2023
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.

2 participants