Scripts in base64 is hard to edit and maintain
Bug #1211336 reported by
Timur Nurlygayanov
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
All our powershell scripts are stored in base64 encoded version. This is hard to maintain and track changes.
We need to move to plain text powershell scripts.
Revision history for this message
| Georgy Okrokvertskhov (gokrokvertskhov) wrote | #1 |
| Changed in murano: | |
| status: | New → Fix Committed |
| Changed in murano: | |
| assignee: | nobody → Georgy Okrokvertskhov (gokrokvertskhov) |
| assignee: | Georgy Okrokvertskhov (gokrokvertskhov) → nobody |
| Changed in murano: | |
| status: | Fix Committed → Fix Released |
| description: | updated |
| Changed in murano: | |
| importance: | High → Medium |
| status: | Fix Released → Fix Committed |
| summary: |
- Scripts in base64 is hard to edit and maintain + Launchpad Bug #1211336: Scripts in base64 is hard to edit and maintain |
| summary: |
- Launchpad Bug #1211336: Scripts in base64 is hard to edit and maintain + Scripts in base64 is hard to edit and maintain |
| Changed in murano: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This issue is fixed by the commit https:/
All scripts now are stored in the plain text format instead of base64 encoded. Scripts referred in a template will be searched in the ./scripts/ folder relatively to the template file folder. This will allow to have your own custom workflows stored separately from common Murano templates and scripts. This will help to avoid conflicts and issues with Murano code upgrade.