8000 azurerm_storage_account: Seeking geo-redundancy enablement for file shares · Issue #28828 · hashicorp/terraform-provider-azurerm · GitHub
[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

azurerm_storage_account: Seeking geo-redundancy enablement for file shares #28828

Open
1 task done
pariswd opened this issue Feb 20, 2025 · 3 comments
Open
1 task done

azurerm_storage_account: Seeking geo-redundancy enablement for file shares #28828

pariswd opened this issue Feb 20, 2025 · 3 comments
Labels
enhancement service/storage

Comments

@pariswd
Copy link
pariswd commented Feb 20, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

Azure supports two storage types for file shares, Standard and Premium, and Standard must be selected to enable geo-redundancy replication. azurerm_storage_account, however, supports only Premium storage for file shares thereby preventing the use of geo-redundancy replication.

The ask: since Azure supports Standard storage for file shares, would it be possible for azurerm_storage_account to support it as well?

Details:

  • azurerm_storage_account is used for creating a storage account
  • account_kind arg is set to "FileStorage" to indicate the storage account will house file shares
  • account_tier arg must be set to "Premium" as stated in the azurerm_storage_account doc
  • Any attempt to set account_tier to "Standard" results in error "account_tier must be set to Premium for File Storage accounts"
  • Any attempt to set account_replication_type to "GRS" (geo-redundancy) results in error "InvalidAccountType: AccountType Premium_GRS is invalid"

New or Affected Resource(s)/Data Source(s)

azurerm_storage_account

Potential Terraform Configuration



References


No response

      		
    

      
  





        



            

              
            

        

      


      
    








      

    



      

  
            


    







      

  
      



  

  @magodo





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Collaborator


      

  


  
    

      

      
            magodo
  

      

      

      commented


        Feb 21, 2025


      
    


  




      


        


  
    

      
          
@pariswd Thanks for raising this request! Would you please kindly provide the document about: Azure supports two storage types for file shares, Standard and Premium, and Standard must be selected to enable geo-redundancy replication?

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @pariswd





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  Author


  


  
    

      

      
            pariswd
  

      

      

      commented


        Feb 21, 2025


      
    


  




      


        


  
    

      
          
When I try Standard + GRS I receive this error:


Error: creating Storage Account (Subscription: "***" Resource Group Name: "***" Storage Account Name: "***"): 
performing Create: unexpected status 400 (400 Bad Request) with error: 
InvalidAccountType: AccountType Premium_GRS is invalid. 
For more information, see - https://aka.ms/storageaccountskus



On viewing that web page under the SkuName heading you can see only Standard_GRS is supported.

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @pariswd





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  Author


  


  
    

      

      
            pariswd
  

      

      

      commented


        Feb 21, 2025


      
    


  




      


        


  
    

      
          
And the notes under the table in Supported Azure Storage services indicate the same limitation, that GRS redundancy for file shares isn't supported for Premium storage:


1 Standard file shares are supported on LRS and ZRS. Standard file shares are supported on GRS and GZRS as long as they're less than or equal to 5 TiB in size.

2 Premium file shares are supported on LRS and ZRS.

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    
















  
  

    

      

  





  




  
  

              

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



  






  
                  




    

  


      
  

    Assignees
  



        

    No one assigned







      


  


  

    Labels
  



    

      

    enhancement

  

    service/storage









      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          
  

    

      

        
          

            
    

    Development
  




              
    
No branches or pull requests







        
      

    

  


      

    

  
      

  

    

      3 participants
    

    

        
          @pariswd 
        
          @magodo 
        
          @rcskosir 
    

  






    

    




    






  

          

        



    



  





    

  


  


          



    



  

    

    

    





    


    

    

  



0