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

2023-08-04 | MAIN --> PROD | DEV (14d88e4) --> STAGING #1721

Merged
merged 2 commits into from
Aug 4, 2023
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 4, 2023

This is an auto-generated pull request to merge main into prod for a staging release on 2023-08-04 with the last commit being merged as 14d88e4

@github-actions github-actions bot added the autogenerated Automated pull request creation label Aug 4, 2023
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@github-actions
Copy link
Contributor Author

github-actions bot commented Aug 4, 2023

Please close and re-open this pull request to ensure that a terraform plan is generated on the PR for the staging deployment after merging.

@asteel-gsa asteel-gsa closed this Aug 4, 2023
@asteel-gsa asteel-gsa reopened this Aug 4, 2023
@asteel-gsa asteel-gsa temporarily deployed to production August 4, 2023 12:40 — with GitHub Actions Inactive
@asteel-gsa asteel-gsa temporarily deployed to staging August 4, 2023 12:40 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor Author

github-actions bot commented Aug 4, 2023

Terraform plan for staging

No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

✅ Plan applied in Deploy to Staging Environment #11

@github-actions
Copy link
Contributor Author

github-actions bot commented Aug 4, 2023

Terraform plan for production

Plan: 2 to add, 1 to change, 2 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement
 <= read (data resources)

Terraform will perform the following actions:

  # module.domain.data.cloudfoundry_app.app will be read during apply
  # (config refers to values not yet known)
 <= data "cloudfoundry_app" "app" {
      + buildpack                  = (known after apply)
      + command                    = (known after apply)
      + disk_quota                 = (known after apply)
      + enable_ssh                 = (known after apply)
      + environment                = (sensitive value)
      + health_check_http_endpoint = (known after apply)
      + health_check_timeout       = (known after apply)
      + health_check_type          = (known after apply)
      + id                         = (known after apply)
      + instances                  = (known after apply)
      + memory                     = (known after apply)
      + name                       = (known after apply)
      + name_or_id                 = "*******"
      + space                      = (known after apply)
      + stack                      = (known after apply)
      + state                      = (known after apply)
    }

  # module.domain.data.cloudfoundry_domain.origin_url will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "cloudfoundry_domain" "origin_url" {
      + domain   = (known after apply)
      + id       = (known after apply)
      + internal = (known after apply)
      + name     = "fac.gov"
      + org      = (known after apply)
    }

  # module.domain.data.cloudfoundry_service.external_domain will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "cloudfoundry_service" "external_domain" {
      + id                  = (known after apply)
      + name                = "external-domain"
      + service_broker_name = (known after apply)
      + service_plans       = (known after apply)
    }

  # module.domain.data.cloudfoundry_space.space will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "cloudfoundry_space" "space" {
      + id       = (known after apply)
      + name     = "production"
      + org      = (known after apply)
      + org_name = "gsa-tts-oros-fac"
      + quota    = (known after apply)
    }

  # module.domain.cloudfoundry_route.origin_route must be replaced
-/+ resource "cloudfoundry_route" "origin_route" {
      ~ domain   = "559e0623-9057-45ef-a9ca-e183df56b4e3" # forces replacement -> (known after apply) # forces replacement
      ~ endpoint = "app.fac.gov" -> (known after apply)
      ~ id       = "************************************" -> (known after apply)
      + port     = (known after apply)
      ~ space    = "5593dba8-7023-49a5-bdbe-e809fe23edf9" # forces replacement -> (known after apply) # forces replacement
        # (1 unchanged attribute hidden)

      - target {
          - app  = "5dac166f-2fb0-4e72-8d4d-4359191bf284" -> null
          - port = 0 -> null
        }
      + target {
          + app  = (known after apply)
          + port = (known after apply)
        }
    }

  # module.domain.cloudfoundry_service_instance.external_domain_instance must be replaced
-/+ resource "cloudfoundry_service_instance" "external_domain_instance" {
      ~ id                             = "************************************" -> (known after apply)
      ~ name                           = "gsa-fac-fac.gov" -> (known after apply)
      ~ service_plan                   = "7c5ed2a5-6734-455f-b1b9-4eaa55f638b3" -> (known after apply)
      ~ space                          = "5593dba8-7023-49a5-bdbe-e809fe23edf9" # forces replacement -> (known after apply) # forces replacement
      - tags                           = [] -> null
        # (4 unchanged attributes hidden)
    }

  # module.production.module.https-proxy.cloudfoundry_app.egress_app will be updated in-place
  ~ resource "cloudfoundry_app" "egress_app" {
        id                              = "5e81ca8b-99cf-41f8-ae42-76652d51a44c"
        name                            = "https-proxy"
      ~ source_code_hash                = "9fcf4a7f6abfc9a220de2b8bb97591ab490a271ac0933b984f606f645319e1a4" -> "9b63bf9766c73480bf1c2385e259b1321988ede71a7b68ebe5c451d9ff6bf1c1"
        # (18 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

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

📝 Plan generated in Pull Request Checks #284

@asteel-gsa asteel-gsa merged commit 8c58267 into prod Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autogenerated Automated pull request creation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants