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

azurerm - storage account resource has no support for custom domains #15

Closed
hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #363
Closed

azurerm - storage account resource has no support for custom domains #15

hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #363
Assignees

Comments

@hashibot
Copy link

This issue was originally opened by @Tasquith as hashicorp/terraform#7800. It was migrated here as part of the provider split. The original body of the issue is below.


I've been looking at the storage account resource and I can't seem to find a way to add a custom domain name, which is supported by the UI.

I've had a look at the API reference, and have found that the required functionality is there (customDomain and useSubDomainName parameters). Are there any plans to implement this?

https://msdn.microsoft.com/en-us/library/azure/mt163564.aspx

Thanks,
Tom

@tombuildsstuff tombuildsstuff self-assigned this Jul 4, 2017
tombuildsstuff added a commit that referenced this issue Sep 28, 2017
- Support for File Encryption. Fixes #80
- Adding Import tests
- Support for Custom Domains on Storage Accounts. Fixes #15
- Splitting the storage account Tier and Replication out into separate fields. Incorporating #117 & Fixing #110
@ghost
Copy link

ghost commented Apr 1, 2020

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants