Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New JsonRPC repo #249

Merged
merged 2 commits into from
Jul 16, 2024
Merged

New JsonRPC repo #249

merged 2 commits into from
Jul 16, 2024

Conversation

phillip-kruger
Copy link
Member

@phillip-kruger phillip-kruger commented Jul 16, 2024

Signed-off-by: Phillip Kruger <phillip.kruger@gmail.com>
@phillip-kruger phillip-kruger requested a review from gastaldi July 16, 2024 03:48
Copy link

github-actions bot commented Jul 16, 2024

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-YsyU5tNyKBD8Uo5b

Waiting for the plan to start...

Terraform v1.9.2
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_repository.quarkus_json_rpc will be created
  + resource "github_repository" "quarkus_json_rpc" {
      + allow_auto_merge            = false
      + allow_merge_commit          = true
      + allow_rebase_merge          = true
      + allow_squash_merge          = true
      + allow_update_branch         = true
      + archive_on_destroy          = true
      + archived                    = false
      + default_branch              = (known after apply)
      + delete_branch_on_merge      = true
      + description                 = "JsonRPC over WebSocket services with Quarkus"
      + etag                        = (known after apply)
      + full_name                   = (known after apply)
      + git_clone_url               = (known after apply)
      + has_issues                  = true
      + homepage_url                = "https://docs.quarkiverse.io/quarkus-json-rpc/dev/"
      + html_url                    = (known after apply)
      + http_clone_url              = (known after apply)
      + id                          = (known after apply)
      + merge_commit_message        = "PR_TITLE"
      + merge_commit_title          = "MERGE_MESSAGE"
      + name                        = "quarkus-json-rpc"
      + node_id                     = (known after apply)
      + primary_language            = (known after apply)
      + private                     = (known after apply)
      + repo_id                     = (known after apply)
      + squash_merge_commit_message = "COMMIT_MESSAGES"
      + squash_merge_commit_title   = "COMMIT_OR_PR_TITLE"
      + ssh_clone_url               = (known after apply)
      + svn_url                     = (known after apply)
      + topics                      = [
          + "json-rpc",
          + "quarkus-extension",
          + "websocket",
        ]
      + visibility                  = (known after apply)
      + vulnerability_alerts        = true
      + web_commit_signoff_required = false

      + security_and_analysis (known after apply)
    }

  # github_team.quarkus_json_rpc will be created
  + resource "github_team" "quarkus_json_rpc" {
      + create_default_maintainer = false
      + description               = "json-rpc team"
      + etag                      = (known after apply)
      + id                        = (known after apply)
      + members_count             = (known after apply)
      + name                      = "quarkiverse-json-rpc"
      + node_id                   = (known after apply)
      + parent_team_id            = "5344029"
      + parent_team_read_id       = (known after apply)
      + parent_team_read_slug     = (known after apply)
      + privacy                   = "closed"
      + slug                      = (known after apply)
    }

  # github_team_membership.quarkus_json_rpc["phillip-kruger"] will be created
  + resource "github_team_membership" "quarkus_json_rpc" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "maintainer"
      + team_id  = (known after apply)
      + username = "phillip-kruger"
    }

  # github_team_membership.quarkus_json_rpc["tecarter94"] will be created
  + resource "github_team_membership" "quarkus_json_rpc" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "maintainer"
      + team_id  = (known after apply)
      + username = "tecarter94"
    }

  # github_team_repository.quarkus_json_rpc will be created
  + resource "github_team_repository" "quarkus_json_rpc" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "maintain"
      + repository = "quarkus-json-rpc"
      + team_id    = (known after apply)
    }

Plan: 5 to add, 0 to change, 0 to destroy.

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

@gastaldi gastaldi merged commit 6077575 into main Jul 16, 2024
2 checks passed
@gastaldi gastaldi deleted the new-json-rpc-repo branch July 16, 2024 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JsonRPC Extension
2 participants