Migrate Terraform from generation to main
The last commit of src/Terraform in generation is:
commit c56cc592d98d948db9a7210bef42da394851ce3f Author: ziyeqf 51212351+ziyeqf@users.noreply.github.com Date: Fri Sep 20 16:59:09 2024 +0800 add new module Az.Terraform to support AzureTerraform RP (#26143)
Checklist
[x] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:
SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
SHOULD make the title of PR clear and informative, and in the present imperative tense.
SHOULD update ChangeLog.md file(s) appropriately
For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. Add changelog in description section if PR goes into generation branch.
Should not change ChangeLog.md if no new release is required, such as fixing test case only.
️✔️Az.Accounts
>
> ️✔️Build
>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>⚠️Az.Terraform
>
> ️✔️Build
>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>
>
> ️✔️Breaking Change Check
>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>
>
> ⚠️Signature Check
>
>>
>> ⚠️PowerShell Core - Windows
>>
>>|Type|Cmdlet|Description|Remediation|
>>|---|---|---|---|
>>|⚠️|New-AzTerraformExportQueryObject|New-AzTerraformExportQueryObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.|
>>|⚠️|New-AzTerraformExportResourceGroupObject|New-AzTerraformExportResourceGroupObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.|
>>|⚠️|New-AzTerraformExportResourceObject|New-AzTerraformExportResourceObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.|
>>
>>
>>
>> ⚠️Windows PowerShell - Windows
>>
>>|Type|Cmdlet|Description|Remediation|
>>|---|---|---|---|
>>|⚠️|New-AzTerraformExportQueryObject|New-AzTerraformExportQueryObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.|
>>|⚠️|New-AzTerraformExportResourceGroupObject|New-AzTerraformExportResourceGroupObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.|
>>|⚠️|New-AzTerraformExportResourceObject|New-AzTerraformExportResourceObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.|
>>
>>
>
>
> ️✔️Help Example Check
>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>
>
> ️✔️Help File Existence Check
>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>
>
> ⚠️File Change Check
>
>>
>> ⚠️PowerShell Core - Windows
>>
>>|Type|Cmdlet|Description|Remediation|
>>|---|---|---|---|
>>|⚠️||It is required to update ChangeLog.md if you want to release a new version for Az.Terraform.|Add a changelog record under Upcoming Release section with past tense.|
>>
>>
>>
>> ⚠️Windows PowerShell - Windows
>>
>>|Type|Cmdlet|Description|Remediation|
>>|---|---|---|---|
>>|⚠️||It is required to update ChangeLog.md if you want to release a new version for Az.Terraform.|Add a changelog record under Upcoming Release section with past tense.|
>>
>>
>
>
> ️✔️UX Metadata Check
>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>
>
> ️✔️Test
>
>>
>> ️✔️PowerShell Core - Linux
>>
>>
>>
>>
>> ️✔️PowerShell Core - MacOS
>>
>>
>>
>>
>> ️✔️PowerShell Core - Windows
>>
>>
>>
>>
>> ️✔️Windows PowerShell - Windows
>>
>>
>>
>
Description
Migrate Terraform from generation to main The last commit of src/Terraform in generation is: commit c56cc592d98d948db9a7210bef42da394851ce3f Author: ziyeqf 51212351+ziyeqf@users.noreply.github.com Date: Fri Sep 20 16:59:09 2024 +0800 add new module
Az.Terraform
to supportAzureTerraform
RP (#26143)Checklist
[x] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:
SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
SHOULD make the title of PR clear and informative, and in the present imperative tense.
SHOULD update ChangeLog.md file(s) appropriately
SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
SHOULD have proper test coverage for changes in pull request.
SHOULD NOT introduce breaking changes in Az minor release except preview version.
SHOULD NOT adjust version of module manually in pull request