[1.x] Allow to customise SystemSettings for BlackBoxContext
#1495
Conversation
This file contains 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
…gs` with `BlackBoxContext` initialized from some `BoundedContextBuilder`.
Add the corresponding tests.
![sonatype-lift[bot]](https://avatars.githubusercontent.com/in/9843?s=60&v=4){kind=small}
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.
Previously, the
BlackBoxContextinstances were built on top ofBoundedContextBuilders by copying the internals of the latter builder. However, not all of the parts were copied properly. Also, this functionality was not tested.This changeset improves the copying by including more pieces from the source
BoundedContextBuilder. In particular, all changes made toBoundedContextBuilder.systemSettings()are now transferred as well.This PR addresses #1485.
Additionally, the
core-javacode was migrated to the freshly updatedio.spine.environmentAPI propagated viabase.Also,
1.x-dev-specific publishing workflow was introduced, along with the required credentials.