-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Support for setting owner and group property on azurerm_storage_data_lake_gen2_filesystem #15547
Comments
@LoW0lf Thank you for submitting this! By looking through the API reference of the data lake gen2 fs, there seems no mention about the Do you know how to do that via the rest API? |
@magodo as far I understand it, this properties don't have to be set on the filesystem itself but on the "/" root directory that comes with the creation of the filesystem. In the current implementation of the filesystem resource, the ace's defined on the filesystem are deployed in the same way, see terraform-provider-azurerm/internal/services/storage/storage_data_lake_gen2_filesystem_resource.go Line 181 in d50e6dd
In code mentioned, the owner and group property is set to nil but from my point of view this should be possible to set them analogue to the path resource. |
This functionality has been released in v2.99.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
In order to properly configure the owning user and owner group (ACL) on a datalake root folder we should have the possibility to configure an AAD object ID for
owner
andgroup
on theazurerm_storage_data_lake_gen2_filesystem
resource analogue to theazurerm_storage_data_lake_gen2_path
resource.New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: