quarkiverse / quarkiverse-devops

Scripts to maintain Quarkiverse repositories
5 stars 13 forks source link

Do not manage branches #246

Closed gastaldi closed 2 months ago

gastaldi commented 2 months ago

This avoids having the branch deleted if the repository is archived by destroying the Terraform file

github-actions[bot] commented 2 months ago

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output ``` Success! The configuration is valid. ```

Terraform Plan 📖success


Running plan in the remote backend. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

The remote workspace is configured to work with configuration at
terraform-scripts relative to the target repository.

Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/quarkiverse-devops/quarkiverse-devops/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
    /home/runner/work/quarkiverse-devops/quarkiverse-devops

To view this run in a browser, visit:
https://app.terraform.io/app/quarkiverse/quarkiverse-devops/runs/run-DKuFakpyzCXxNxZg

Waiting for the plan to start...

Terraform v1.9.1
on linux_amd64
Initializing plugins and modules...

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Pusher: @gastaldi, Action: pull_request, Workflow: Terraform