Release 2.5.0 #943
Merged
Release 2.5.0 #943
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
* PBM_tests. Add delay for PITR to catch-up * PBM_tests. Return OL8 as base image, fix style error
the generator is seeded randomly at program startup
* Introduce MongoOption functional options * Apply new interface for pkg connect * Add doc for connect.Connect func
This reverts commit 2ba76fc.
* Add WriteConcern option * Add ConnectTimeout & ServerSelectionTimeout option * Reuse MongoConnect within physical restore * Use single node write concern for standalone mode
Fix var shadowing in describe-backup with collection
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, mikepenz/action-junit-report@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
* Add users&roles flag for restore cmd * Extract parse namespace into util * Add validation for restoring user&roles for specific collection * Extract user&roles validation for restore cmd * Add tests for ns helper funcs * Add logical selective restore with users and roles * Extract method for restoring users&roles * Add logic for config server selective restore * Add tests for resolving ns and users&roles opt
…storage params are the same (#935) * Fix unnecessary resync op after config is applied ... without any change PBM triggers resync operation in case when any storage parameter has been changed. If the config file and actual config doc in db have the same storage level parameters, resync operation is unnecessary. * Remove storage provider aligment hack
* Add read/write concerns options for commands * Set read/write concern for command type
#940) * Expand RS status with WriteMajorityCount field * Add topo.IsWriteMajorityRequested to determine if majority is requested in current setup * Fix PITR slicing intervals for the case when cluster doesn't have majority
* Improve validation for read concern * Add conn level read/write concerns in logs
sandraromanchenko
approved these changes
May 16, 2024
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.
No description provided.