Repository navigation
Replace infrastructure scripts with Vault Agent, Ansible, and Flyway - #40
Merged
Merged
Conversation
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.
Replace custom Java and Python infrastructure tooling with native lifecycle management.
Docker Compose manages infrastructure dependencies, networking, application startup, and migration jobs. Vault Agent handles authentication, credential delivery, renewal, and application restarts when credentials change. Ansible manages provisioning, initialization, configuration, backup, and recovery operations. Flyway CLI runs independent migrations for Identity, Wallet, Loan, and Collateral.
Remove the root
scripts/directory and obsolete Java migration, import, and leased-datasource implementations. Application KV access now reads the Agent token file.Retain existing volume identities, PostgreSQL 18 layout checks, verified TLS, scoped database roles, and existing versioned SQL migrations. Preserve the committed module names and business implementations.
Validation
Live integration, credential renewal and rotation, failure recovery, backup restoration, and business end-to-end testing remain required before deployment.