-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added script upgrade from 0.5 to 0.6. #643
base: branch-0.17.0-0.6
Are you sure you want to change the base?
Added script upgrade from 0.5 to 0.6. #643
Conversation
…ero/kind into feature/PLT-800_script-upgrade
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lreciomelero he cogido la PR de vuelta pensando que habías terminado de aplicar cambios pero luego he visto que no y que aún quedan pendientes. No obstante te envío respuesta a los comentarios que habías dejado. Por favor, pide una nueva revisión cuando termines de verlo todo. ¡Gracias!
@@ -0,0 +1,154 @@ | |||
= Upgrade Provisioner Script |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pues te compro lo de aprovisionador por Cloud Provisioner, porque como dices, es el nombre del componente. De hecho, lo correcto sería "Script de actualización de Stratio Cloud Provisioner", pero estando en la documentación de Stratio Cloud Provisioner creo que no es necesario repetir esto, por lo que lo dejaría en "Script de actualización".
Lo que no veo es dejar "upgrade", que es una palabra en inglés que tiene traducción y por ello siempre la utilizamos en la documentación de manera traducida. A veces se traduce por actualización a secas y otra por actualización de versión. ¿Cómo lo ves?
"Script de actualización de versión"
|
||
=== Construcción de contenedor de upgrade | ||
|
||
Es necesario ejecutar el contenedor Docker utilizando la imagen de upgrade. En él dispondremos del script y del resto de archivos necesarios para ejecutar el proceso: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remito al comentario anterior, no sería correcto utilizar la palabra en inglés cuando se puede traducir, a no ser que sea el nombre de algo y vaya en inglés... ¿si ponemos "la imagen de actualización de versión" lo ves mejor?
|
||
- Para otros entornos, elimine la sección `images`. | ||
|
||
=== Script de Upgrade |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mismo comentario.
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Co-authored-by: Teresa Pérez Senso <[email protected]>
Description
Please add the PR description here.
Related Pull Requests
Pull Request Checklist: