Upgrade Porter to v1 #3014
Upgrade Porter to v1 #3014
Conversation
|
/test-extended |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/3780421538 (with refid (in response to this comment from @tamirkamara) |
1 similar comment
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/3780421538 (with refid (in response to this comment from @tamirkamara) |
|
/test-extended |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/3781052944 (with refid (in response to this comment from @tamirkamara) |
* porter v1 core * cr changes * some fixes * workflow triggers * api version * include porter's config.yaml
* templates change for porter v1 * fix exit code when retrying * fix guacamole * certbot doesn't need to install python * debug porter explain * cleanup * lint * rp version * cr comments * fix base workflow conflict
update docs for porter v1
tamirkamara
force-pushed
the
feature/porter-v1
branch
from
64348c9 to
4d60e70
Compare
|
/test-force-approve |
|
🤖 pr-bot 🤖 ✅ Marking tests as complete (for commit 4d60e70) (in response to this comment from @tamirkamara) |
Resolves #2755, Resolves #1828
What is being addressed
Porter v1 has been released recently and we need to upgrade.
How is this addressed
Many small changes were made to support this upgrade. You can review the notes on the separate PRs comprising this one.
You are required to upgrade any existing template - edit its definition per the new schema (use any template in this repo as an example), and register a new version for all templates you're using.