Closed gastaldi closed 6 months ago
success
success
success
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-VDgVWi1qULb3ubzF
Waiting for the plan to start...
Terraform v1.7.3
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
~ update in-place
Terraform will perform the following actions:
# github_team_membership.quarkus_hivemq_client["codepitbull"] will be created
+ resource "github_team_membership" "quarkus_hivemq_client" {
+ etag = (known after apply)
+ id = (known after apply)
+ role = "maintainer"
+ team_id = "4651319"
+ username = "codepitbull"
}
# github_team_membership.quarkus_jnosql["otaviojava"] will be created
+ resource "github_team_membership" "quarkus_jnosql" {
+ etag = (known after apply)
+ id = (known after apply)
+ role = "maintainer"
+ team_id = "7580477"
+ username = "otaviojava"
}
# github_team_membership.quarkus_kafka_streams_processor["bsoaressimoes"] will be created
+ resource "github_team_membership" "quarkus_kafka_streams_processor" {
+ etag = (known after apply)
+ id = (known after apply)
+ role = "maintainer"
+ team_id = "9184809"
+ username = "bsoaressimoes"
}
# github_team_membership.quarkus_kafka_streams_processor["ivantchomgue1a"] will be created
+ resource "github_team_membership" "quarkus_kafka_streams_processor" {
+ etag = (known after apply)
+ id = (known after apply)
+ role = "maintainer"
+ team_id = "9184809"
+ username = "ivantchomgue1a"
}
# github_team_membership.quarkus_univocity_parsers["aruffie"] will be created
+ resource "github_team_membership" "quarkus_univocity_parsers" {
+ etag = (known after apply)
+ id = (known after apply)
+ role = "maintainer"
+ team_id = "4707008"
+ username = "aruffie"
}
# github_team_repository.quarkus_microprofile will be updated in-place
~ resource "github_team_repository" "quarkus_microprofile" {
id = "5018652:quarkus-microprofile"
~ permission = "admin" -> "maintain"
# (3 unchanged attributes hidden)
}
Plan: 5 to add, 1 to change, 0 to destroy.
Pusher: @gastaldi, Action: pull_request
, Workflow: Terraform
I guess it requires approval by @amoscatelli and @dearrudam
@quarkiverse/quarkiverse-jnosql any thoughts?
@gastaldi I agree to grant the "maintainer" access to @otaviojava! I believe that it will boost the project's evolution and enhance community engagement in the project! @otaviojava, as the leader and maintainer of the Eclipse JNoSQL, is a valuable addition to this project, he will bring the best support to this extension.
Agreed, let's do this
@otaviojava welcome aboard the Quarkiverse
@otaviojava welcome aboard the Quarkiverse
Thank you @gastaldi :)
This gives @otaviojava maintainer access to https://github.com/quarkiverse/quarkus-jnosql