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

Introduce quarkus-sqlite4j #319

Merged
merged 1 commit into from
Feb 4, 2025
Merged

Introduce quarkus-sqlite4j #319

merged 1 commit into from
Feb 4, 2025

Conversation

gastaldi
Copy link
Member

@gastaldi gastaldi commented Feb 4, 2025

```
- Introduce Terraform script to automate creation and access configuration for the Quarkus SQLite4j GitHub repository.
- Configure code ownership for the Quarkus SQLite4j Terraform module to ensure maintainability and review standards.
```
Copy link

github-actions bot commented Feb 4, 2025

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

Waiting for the plan to start...

Terraform v1.10.5
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_sqlite4j will be created
  + resource "github_repository" "quarkus_sqlite4j" {
      + 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                 = "SQLite driver for Quarkus with Agroal in pure Java built on SQLite4j"
      + 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-sqlite4j/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-sqlite4j"
      + 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                      = [
          + "quarkus-extension",
        ]
      + visibility                  = (known after apply)
      + vulnerability_alerts        = true
      + web_commit_signoff_required = false

      + security_and_analysis (known after apply)
    }

  # github_team.quarkus_sqlite4j will be created
  + resource "github_team" "quarkus_sqlite4j" {
      + create_default_maintainer = false
      + description               = "sqlite4j team"
      + etag                      = (known after apply)
      + id                        = (known after apply)
      + members_count             = (known after apply)
      + name                      = "quarkiverse-sqlite4j"
      + 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_sqlite4j["andreaTP"] will be created
  + resource "github_team_membership" "quarkus_sqlite4j" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "maintainer"
      + team_id  = (known after apply)
      + username = "andreaTP"
    }

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

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

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

@gastaldi gastaldi merged commit 78e9831 into main Feb 4, 2025
2 checks passed
@gastaldi gastaldi deleted the sqlite4j branch February 4, 2025 21:08
@melloware
Copy link
Contributor

@gastaldi for consistency shouldn't it be quarkus-jdbc-sqlite4j to be consistent with other JDBC extensions?

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.

[Extension Proposal] SQLite4j JDBC - sqlite in pure java
2 participants