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

Features - Initial implementation of Azure NetApp File #226

Closed
4 tasks
arnaudlh opened this issue Jan 13, 2021 · 1 comment · Fixed by #235
Closed
4 tasks

Features - Initial implementation of Azure NetApp File #226

arnaudlh opened this issue Jan 13, 2021 · 1 comment · Fixed by #235
Assignees

Comments

@arnaudlh
Copy link
Member

arnaudlh commented Jan 13, 2021

Initial implementation of Azure NetApp Files:

  • azurerm_netapp_account
  • azurerm_netapp_pool
  • azurerm_netapp_snapshot
  • azurerm_netapp_volume
@xpillons
Copy link
Collaborator

@arnaudlh there is a need for additional CAF random names for netapp account, pools and volume. Here are the rules to follow :

  • Account must be unique for the subscription.
  • Capacity pool name must be unique for each NetApp account
  • A volume name must be unique within each capacity pool. It must be at least three characters long. You can use any alphanumeric characters.

@arnaudlh arnaudlh linked a pull request Jan 27, 2021 that will close this issue
BerendvW pushed a commit to VolkerWessels/terraform-azurerm-caf that referenced this issue Jun 21, 2023
Add support for Hashicorp vault secret backend role
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 a pull request may close this issue.

2 participants