feat: Parametrization of MongoDB persistence for localhost and GCP #1303
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.
Motivation
Based on the new feature introduced by aneoconsulting/ArmoniK.Infra#153, this PR enables different persistence configuration for both localhost and GCP deployments, as it is already done for AWS.
Description
It includes a new object persistent_volume in the mongodb variable. If it is null, persistence is disabled as it was before, else, persistence is enabled under the condition that the configuration provided fits you cluster.
Testing
Deployed on GCP and localhost.
Impact
More flexibility with MongoDB persistence for GCP and localhost.
Additional Information
Checklist