@ -74,6 +74,10 @@ variables using
use the terraform configuration below. Please make sure all the requirements of
use the terraform configuration below. Please make sure all the requirements of
azure-gh-actions are followed before running it.
azure-gh-actions are followed before running it.
**NOTE:** When running the following for a repo under an organization, set the
environment variable `GITHUB_ORGANIZATION` if setting the `owner` in the
`github` provider doesn't work.
```hcl
```hcl
provider "github" {
provider "github" {
owner = "fluxcd"
owner = "fluxcd"
@ -218,7 +222,7 @@ variables using
use the terraform configuration below. Please make sure all the requirements of
use the terraform configuration below. Please make sure all the requirements of
gcp-gh-actions are followed before running it.
gcp-gh-actions are followed before running it.
**NOTE:** When running the following for a repo under and organization, set the
**NOTE:** When running the following for a repo under an organization, set the
environment variable `GITHUB_ORGANIZATION` if setting the `owner` in the
environment variable `GITHUB_ORGANIZATION` if setting the `owner` in the
`github` provider doesn't work.
`github` provider doesn't work.
@ -345,8 +349,13 @@ We also pull two version of `ghcr.io/stefanprodan/podinfo` image. These images a
Container Registry and used to test `ImageRepository` and `ImageUpdateAutomation` . The terraform resources get created
Container Registry and used to test `ImageRepository` and `ImageUpdateAutomation` . The terraform resources get created
and the tests are run.
and the tests are run.
**IMPORTANT:** In case the terraform infrastructure results in a bad state, maybe due to a crash during the apply,
If not configured explicitly to retain the infrastructure, at the end of the
the whole infrastructure can be destroyed by running terraform destroy in terraform/< provider > directory.
test, the test infrastructure is deleted. In case of any failure due to which
the resources don't get deleted, the `make destroy-*` commands can be run for
the respective provider. This will run terraform destroy in the respective
provider's terraform configuration directory. This can be used to quickly
destroy the infrastructure without going through the provision-test-destroy
steps.
### Debugging the tests
### Debugging the tests