https://github.com/hashicorp/terraform-provider-azure-classic

Terraform Azure Classic (Service Management) provider
https://github.com/hashicorp/terraform-provider-azure-classic

azure-classic terraform terraform-provider

Last synced: about 1 month ago
JSON representation

Terraform Azure Classic (Service Management) provider

• Host: GitHub
• URL: https://github.com/hashicorp/terraform-provider-azure-classic
• Owner: hashicorp
• License: mpl-2.0
• Archived: true
• Created: 2017-06-05T20:54:14.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-10-10T19:32:11.000Z (about 6 years ago)
• Last Synced: 2024-09-24T06:31:21.033Z (about 1 month ago)
• Topics: azure-classic, terraform, terraform-provider
• Language: Go
• Homepage: https://www.terraform.io/docs/providers/azure/
• Size: 5.51 MB
• Stars: 2
• Watchers: 9
• Forks: 11
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE
  • Code of conduct: .github/CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
# Terraform Provider for Azure Classic

## Please Note

This repository is for the Terraform Provider for Azure Classic (also known as Service Management / "the old Portal").

Today (December 19, 2017) [we’ve announced the deprecation and archival of the Azure Classic Provider](https://hashicorp.com/blog/deprecating-the-microsoft-azure-legacy-asm-terrafor). Matching Microsoft’s commitment to gradually remove access to Azure Classic (or Service Management) [which is outlined in this blog post](https://azure.microsoft.com/en-us/updates/azure-portal-updates-for-classic-portal-users/), we are closing all open PR's and Issues here. This repository will remain available here on GitHub, but in an archived state, and no longer receiving support or new releases.

[The Azure (Resource Manager) Provider](https://github.com/terraform-providers/terraform-provider-azurerm) remains fully supported and is our recommended approach for managing Azure with Terraform. More information about this process is available in the blog post linked above.