feat: include mongodb retry skip index creation parameter #162
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
mauriciomoccelin
force-pushed
the
feat/mongo-db-retry-skip-index-creation
branch
from
b140043 to
ebb754d
Compare
wesleyalvarenga
approved these changes
Aug 21, 2025
EvaldRafael
approved these changes
Aug 22, 2025
When this parameter is included, the application will ignore the creation of its indexes. This makes the behavior explicit for the developer using the library.
mauriciomoccelin
force-pushed
the
feat/mongo-db-retry-skip-index-creation
branch
from
e6221e9 to
c1d2463
Compare
caiocanallipagarme
approved these changes
Aug 25, 2025
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.
Description
This PR introduces a new configuration parameter that allows developers to explicitly skip automatic MongoDB index creation in KafkaFlow.Retry.MongoDb.
By setting this option, the library will create collections but will not enforce index creation. This provides greater flexibility in environments where indexes are managed externally (e.g., via migrations, DevOps pipelines, or centralized governance).
Fixes #161
Motivation and Context
Currently, indexes are automatically created through
DboConfigurations.TryAddIndexes. While convenient in development, this behavior may conflict with existing database policies in production environments.The new parameter makes index management explicit, giving developers control and avoiding duplicate or conflicting index definitions.
How Has This Been Tested?
Unit tests were added to validate that:
Integration tests confirm that collections are still created and functional even when index creation is disabled.
Checklist
Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our [Contributor Ownership Statement](https://github.com/Farfetch/.github/blob/master/COS.md)