PLAT-606 Rename services to be consistent [DONT MERGE] #205
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
nour-borgi
changed the base branch from
main
to
PLAT-606-general-refactoring-part-3
Base automatically changed from
PLAT-606-general-refactoring-part-3
to
PLAT-606-exit-error-bash
January 11, 2023 08:34
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.
[DON'T MERGE] for this reason:
Renaming the services such as Postgres and Mongo will lead to the creation of new volumes
We need to deploy the backup functionality to save the backup and the deploy this change then restoring after that.
For example, the hapi-postgres-3-data volume will change to hapi-postgres-03-data, which means the data will be connected to the previous volume, not the new one that will be created.