Remove in-memory storage engine, refactor config logic #94
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.
By convention, Infratographer CRDB configs should be a top-level config item. In reconfiguring this, a number of other things shook out including no longer needing (or necessarily even wanting) a separate in-memory storage engine. The dev container supports a database now and we can just create CRDB test servers as needed for testing. This commit refactors the storage package to take a
crdbx
config directly and defines migrations, tracing, and database seeding as options on the storage engine.