Transfert/migration S3 de Scaleway vers OVH #1200
Open
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
|
Attention : bien s'assurer que le direct upload des photos fonctionne toujours dans l'application après la migration vers OVH |
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.
Actuellement nos photos et bordereaux de récolement sont hébergés sur un bucket S3 chez Scaleway.
Dans le cadre du transfert vers l'infrastructure du ministère, nous allons passer sur un S3 hébergé chez OVH.
Avant de passer de l'un à l'autre, on doit s'assurer d'avoir bien copié le contenu du bucket Scaleway vers le nouveau bucket OVH.
On en profite pour supprimer les reliquats de configuration
project_coetproject_defaultsIl y a un bucket par environnement, que l'on nomme en conséquence
collectif-objets-environnement