Refactor applications scripts to make it more clear and fault-tolerant
Some applications use scripts that contain a large list of different actions, lumped together in a single file. It spoils the readability of the app implementation and may lead to a situation when one command in a middle of the script fails with an error, but the last command is successful - so, the result of whole script is successful too.
For example, ww have next script for apache installation: https:/
First part of script installs application and second configures firewall. It can be easily devided to two scripts.
We need to logically divide all existing scripts according to functionality and add the checks for the command to stop execution when it fails.
Blueprint information
- Status:
- Not started
- Approver:
- Serg Melikyan
- Priority:
- Undefined
- Drafter:
- Dmytro Dovbii
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
[ApacheHTTP
Addressed by: https:/
{WIP} Refactor implementation of murano apllications
Addressed by: https:/
Use simple software configuration instead of EP
Addressed by: https:/
[MySql] Use simple software configuration
Addressed by: https:/
[WordPress] Use simple software configuration
Addressed by: https:/
[MongoDB] Use simple software configuration
Addressed by: https:/
[Cassandra] Use simple software configuration
Addressed by: https:/
[Guacamole] Use simple software configuration
Addressed by: https:/
[Rally] Use simple software configuration
Addressed by: https:/
[Tomcat] Use simple software configuration
Addressed by: https:/
[ZabbixServer] Use simple software configuration
Addressed by: https:/
[PostgreSql] Use simple software configuration
Addressed by: https:/
Fix yaql related issues in Docker apps
