Skip to content

Test - Failed plan #374

Test - Failed plan

Test - Failed plan #374

Manually triggered December 6, 2023 20:28
Status Failure
Total duration 51s
Artifacts

test-failed-plan.yml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
test
no submodule mapping found in .gitmodules for path 'components/terraform/foobar/.terraform/modules/this'
test
Process completed with exit code 1.
assert
Expected '## Plan Failed for `foobar-fail` in `plat-ue2-sandbox` <a href="https://cloudposse.com/"><img src="https://cloudposse.com/logo-300x69.svg" width="100px" align="right"/></a> [![failed](https://shields.io/badge/PLAN-FAILED-ff0000?style=for-the-badge)](#user-content-result-plat-ue2-sandbox-foobar-fail) <details><summary><a id="result-plat-ue2-sandbox-foobar-fail" />:warning: Error summary</summary> <br/> To reproduce this locally, run:<br/><br/> ```shell atmos terraform plan foobar-fail -s plat-ue2-sandbox ``` --- ```hcl Error: Failed to install provider Error while installing hashicorp/random v3.6.0: mkdir .terraform/providers/registry.terraform.io/hashicorp/random/3.6.0/linux_amd64: file exists exit status 1 ``` </details>' to equal '## Plan Failed for `foobar-fail` in `plat-ue2-sandbox` <a href="https://cloudposse.com/"><img src="https://cloudposse.com/logo-300x69.svg" width="100px" align="right"/></a> [![failed](https://shields.io/badge/PLAN-FAILED-ff0000?style=for-the-badge)](#user-content-result-plat-ue2-sandbox-foobar-fail) <details><summary><a id="result-plat-ue2-sandbox-foobar-fail" />:warning: Error summary</summary> <br/> To reproduce this locally, run:<br/><br/> ```shell atmos terraform plan foobar-fail -s plat-ue2-sandbox ``` --- ```hcl Error: Invalid function argument on main.tf line 10, in locals: 10: failure = var.enable_failure ? file("Failed because failure mode is enabled") : null ├──────────────── │ while calling file(path) Invalid value for "path" parameter: no file exists at "Failed because failure mode is enabled"; this function works only with files that are distributed as part of the configuration source code, so if this file will be created by a resource in this configuration you must instead obtain this result from an attribute of that resource. exit status 1 ``` </details>'
test
Unable to clean or reset the repository. The repository will be recreated instead.
test
The process '/usr/bin/git' failed with exit code 128
test
The process '/usr/bin/git' failed with exit code 128