Conversation
* Removing sling * Adding deprecation warnings * Removing sling-based dumper * Linting
* adding the necessary code for the admin panel changes * adding a test for the uei ein changes * uei/ein change migrations * test edit record admin wpi * Adding auditee_name to the command * Reverting to `curs.execute()` * Admin command fixes, reduced complexity, and linting * Test fixed for admin command. Mocks out the CurationTracking! * Typo fixes :) * adding the curation tracking fix to auditee name as well * lint fix on test_edit_record_admin * lint fixes * removing Audit import * adding another new line for lint * adding another new line for lint on MockRequest * lint change * Linting! Yay! * Migration check in all Django apps * Banish some old comments + an unused function, a little cleanup. * Curation audit tracking, always `init` at least once. * Solidifying the Django connection path for management commands. * LINTING! YES! * Rename `enabled` to `initiaized`. It makes way more sense. * changes to the edit record narrowing down input options to just one * black applied to models.py * breaking out the option dictionary into its own function * black fixes * `black`, with v2026 --------- Co-authored-by: James Person <jperson1@umbc.edu> Co-authored-by: James Person <james.person@gsa.gov>
Contributor
|
Terraform plan for production Plan: 1 to add, 0 to change, 1 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# module.production.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~ id = "*******************" -> (known after apply)
!~ triggers = { # forces replacement
!~ "always_run" = "2026-04-29T18:00:31Z" -> (known after apply)
}
}
Plan: 1 to add, 0 to change, 1 to destroy.📝 Plan generated in Pull Request Checks #876 |
Contributor
|
Terraform plan for staging Plan: 1 to add, 0 to change, 1 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# module.staging.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~ id = "*******************" -> (known after apply)
!~ triggers = { # forces replacement
!~ "always_run" = "2026-04-30T11:03:02Z" -> (known after apply)
}
}
Plan: 1 to add, 0 to change, 1 to destroy.📝 Plan generated in Pull Request Checks #876 |
Contributor
Minimum allowed line rate is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an auto-generated pull request to merge main into prod for a staging release on 2026-04-30 with the last commit being merged as d994839