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-7G6hX5zuJx7NCtph
Waiting for the plan to start...
Terraform v1.9.7
on linux_amd64
Initializing plugins and modules...
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# github_repository.quarkus_itext will be updated in-place
~ resource "github_repository" "quarkus_itext" {
~ description = "Create and manipulate PDFs on the fly" -> "Create and manipulate PDFs on the fly with iText/OpenPDF"
~ homepage_url = "https://github.com/albfernandez/itext2" -> "https://github.com/LibrePDF/OpenPDF"
id = "quarkus-itext"
name = "quarkus-itext"
~ topics = [
- "graalvm",
+ "openpdf",
# (5 unchanged elements hidden)
]
# (33 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Terraform Format and Style 🖌
success
Terraform Initialization ⚙️
success
Terraform Validation 🤖
success
Validation Output
``` Success! The configuration is valid. ```Terraform Plan 📖
success
Pusher: @melloware, Action:
pull_request
, Workflow:Terraform