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

Sync quarkus-resteasy-problems settings #252

Merged
merged 1 commit into from
Jul 18, 2024
Merged

Sync quarkus-resteasy-problems settings #252

merged 1 commit into from
Jul 18, 2024

Conversation

gastaldi
Copy link
Member

No description provided.

@gastaldi gastaldi requested a review from a team as a code owner July 18, 2024 14:24
Copy link

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

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
  ~ update in-place

Terraform will perform the following actions:

  # github_repository.quarkus_resteasy_problem will be updated in-place
  ~ resource "github_repository" "quarkus_resteasy_problem" {
      ~ allow_merge_commit          = false -> true
      ~ allow_rebase_merge          = false -> true
      ~ allow_update_branch         = false -> true
      + archive_on_destroy          = true
      ~ description                 = "Unified error responses for Quarkus REST APIs via Problem Details for HTTP APIs (RFC9457 & RFC7807). Supports Quarkus 3.0+, 2.0+ and 1.4+." -> "Unified error responses for Quarkus REST APIs via Problem Details for HTTP APIs (RFC9457 & RFC7807)"
      + homepage_url                = "https://docs.quarkiverse.io/quarkus-resteasy-problem/dev"
        id                          = "quarkus-resteasy-problem"
        name                        = "quarkus-resteasy-problem"
      ~ topics                      = [
          - "java",
          - "json",
          - "problem",
          - "quarkus",
          - "rest",
          + "rest-problem",
            # (5 unchanged elements hidden)
        ]
        # (30 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # github_team_repository.quarkus_resteasy_problem will be created
  + resource "github_team_repository" "quarkus_resteasy_problem" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "maintain"
      + repository = "quarkus-resteasy-problem"
      + team_id    = "10592369"
    }

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

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

@gastaldi gastaldi merged commit b6150d7 into main Jul 18, 2024
2 checks passed
@gastaldi gastaldi deleted the problems branch July 18, 2024 14:29
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.

2 participants