github-actions[bot]
commented
1 month 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-19nTk3EDJhE7MwsZ
Waiting for the plan to start...
Terraform v1.9.8
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:
+ create
Terraform will perform the following actions:
# github_team_membership.quarkus_playwright["melloware"] will be created
+ resource "github_team_membership" "quarkus_playwright" {
+ etag = (known after apply)
+ id = (known after apply)
+ role = "maintainer"
+ team_id = "8521269"
+ username = "melloware"
}
Plan: 1 to add, 0 to change, 0 to destroy.
Pusher: @ia3andy, Action: pull_request, Workflow: Terraform
gastaldi
cc @ia3andy is this OK so I can keep the Playwright plugin up to date?