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

Clarify disable as user deletion #3360

Merged
merged 1 commit into from
Mar 11, 2024
Merged

Conversation

mgyucht
Copy link
Contributor

@mgyucht mgyucht commented Mar 11, 2024

Changes

disable_as_user_deletion is a bit confusing for users. This PR updates the docs to make its behavior more obvious.

Tests

  • make test run locally
  • relevant change in docs/ folder
  • covered with integration tests in internal/acceptance
  • relevant acceptance tests are passing
  • using Go SDK

@mgyucht mgyucht requested review from a team as code owners March 11, 2024 12:44
@mgyucht mgyucht requested review from tanmay-db and removed request for a team March 11, 2024 12:44
* `force_delete_repos` - (Optional) This flag determines whether the service principal's repo directory is deleted when the user is deleted. It will have no impact when in the accounts SCIM API. False by default.
* `force_delete_home_dir` - (Optional) This flag determines whether the service principal's home directory is deleted when the user is deleted. It will have no impact when in the accounts SCIM API. False by default.
* `disable_as_user_deletion` - (Optional) When deleting a user, set the user's active flag to false instead of actually deleting the user. This flag is exclusive to force_delete_repos and force_delete_home_dir flags. True by default for accounts SCIM API, false otherwise.
- `application_id` - This is the Azure Application ID of the given Azure service principal and will be their form of access and identity. On other clouds than Azure this value is auto-generated.
Copy link
Contributor

Choose a reason for hiding this comment

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

Since all other fields have Optional / Required, it would be good to specify it here as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The note immediately before this explains this field:

application_id is required on Azure Databricks and is not allowed on other clouds.

@mgyucht mgyucht added this pull request to the merge queue Mar 11, 2024
Merged via the queue into main with commit 64ffcac Mar 11, 2024
5 checks passed
@mgyucht mgyucht deleted the clarify-disable-as-user-deletion branch March 11, 2024 14:51
@hectorcast-db hectorcast-db mentioned this pull request Mar 28, 2024
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.

3 participants