destroy-command #131
Triggered via repository dispatch
September 7, 2023 02:12
hc-team-tfe
hc-team-tfe
destroy-command
ce17e13
Status
Success
Total duration
10m 51s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
handler-destroy.yml
on: repository_dispatch
Destroy resources from Azure Private TCP Active/Active
/
Run tf-test on some azure infrastructure
10m 40s
Destroy resources from Azure Private Active/Active
/
Run tf-test on some azure infrastructure
Destroy resources from Azure Public Active/Active
/
Run tf-test on some azure infrastructure
Destroy resources from Azure Standalone External
/
Run tf-test on some azure infrastructure
Destroy resources from Azure Standalone Mounted Disk
/
Run tf-test on some azure infrastructure
Annotations
2 warnings
|
Destroy resources from Azure Private TCP Active/Active / Run tf-test on some azure infrastructure
The following actions uses node12 which is deprecated and will be forced to run on node16: hashicorp/setup-terraform@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Destroy resources from Azure Private TCP Active/Active / Run tf-test on some azure infrastructure
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|