-
Notifications
You must be signed in to change notification settings - Fork 198
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
Create an alpha
version of azure.yaml
schema
#2251
Conversation
Here's a diff between the two schemas. --- ./schemas/v1.0/azure.yaml.json 2023-05-03 21:41:49
+++ ./schemas/alpha/azure.yaml.json 2023-05-17 11:54:11
@@ -1,6 +1,6 @@
{
"$schema": "https://json-schema.org/draft/2019-09/schema",
- "$id": "https://raw.githubusercontent.com/Azure/azure-dev/main/schemas/v1.0/azure.yaml.json",
+ "$id": "https://raw.githubusercontent.com/Azure/azure-dev/main/schemas/alpha/azure.yaml.json",
"type": "object",
"required": [
"name"
@@ -42,7 +42,8 @@
"title": "Type of infrastructure provisioning provider",
"description": "Optional. The infrastructure provisioning provider used to provision the Azure resources for the application. (Default: bicep)",
"enum": [
- "bicep"
+ "bicep",
+ "terraform"
]
},
"path": { |
We don't want to include any values in the schema that are tied to alpha features in the `v1.0` schema, since we may remove or change these values during development. This change introduces a new copy of this schema and adds "terraform" as a supported member of an enum (this is a new value that is supported behind an alpha feature) Fixes Azure#1925
/check-enforcer override |
Should we also update the TF todo templates with the alpha schema as part of this PR? |
Pushed 3aaaa3c to reference these in the bicep templates, @savannahostrowski. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! We should also probably let the ASA team know to update their template as well!
Repoman Generation ResultsRepoman pushed changes to remotes for the following projects: Project: azd-starter-terraformRemote: azure-samples-stagingBranch: pr/2251You can initialize this project with: azd init -t Azure-Samples/azd-starter-terraform -b pr/2251 View Changes | Compare Changes Project: todo-java-postgresql-terraformRemote: azure-samples-stagingBranch: pr/2251You can initialize this project with: azd init -t Azure-Samples/todo-java-postgresql-terraform -b pr/2251 View Changes | Compare Changes Project: todo-nodejs-mongo-terraformRemote: azure-samples-stagingBranch: pr/2251You can initialize this project with: azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/2251 View Changes | Compare Changes Project: todo-python-mongo-terraformRemote: azure-samples-stagingBranch: pr/2251You can initialize this project with: azd init -t Azure-Samples/todo-python-mongo-terraform -b pr/2251 View Changes | Compare Changes |
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSIContainer
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference (preview)
|
We don't want to include any values in the schema that are tied to alpha features in the
v1.0
schema, since we may remove or change these values during development.This change introduces a new copy of this schema and adds "terraform" as a supported member of an enum (this is a new value that is supported behind an alpha feature)
Fixes #1925