-
Notifications
You must be signed in to change notification settings - Fork 138
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
Pipeline Property Substitution #2052
Conversation
Unit Test Results288 tests +287 286 ✔️ +285 9s ⏱️ - 31m 24s Results for commit 0c60bf7. ± Comparison against base commit 16f4c60. This pull request removes 1 and adds 288 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2510104310 (with refid (in response to this comment from @damoodamoo) |
/test-destroy-env |
Destroying branch test environment (RG: rg-trec7302e0e)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2510319711) |
Destroying PR test environment (RG: rg-tre4e00469a)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2510319711) |
Branch test environment destroy complete (RG: rg-trec7302e0e) |
PR test environment destroy complete (RG: rg-tre4e00469a) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2510424861 (with refid (in response to this comment from @damoodamoo) |
Love it. Might be worth someone looking over the code - not sure I can give it the service it deserves. Would be good to know what is/isn't supported - for example could I upgrade a workspace with a new property? |
api_app/tests_ma/test_service_bus/test_resource_request_sender.py
Outdated
Show resolved
Hide resolved
api_app/tests_ma/test_service_bus/test_resource_request_sender.py
Outdated
Show resolved
Hide resolved
The docs say only "shared-services" are supported at the moment. |
Co-authored-by: Ross Smith <ross-p-smith@users.noreply.github.com>
Co-authored-by: Ross Smith <ross-p-smith@users.noreply.github.com>
Co-authored-by: Ross Smith <ross-p-smith@users.noreply.github.com>
Co-authored-by: Ross Smith <ross-p-smith@users.noreply.github.com>
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.
I didn't review the logic and would only comment:
- If gitea/nexues don't need azcli anymore, can you please delete the dockerfile.tmpl as well (from the porter.yaml too)
- Would merging still make it possible to use the "old" firewall script (as we do so elsewhere), or does it need to be upgrades in the other places immediately?
I have only removed the firewall terraform resources in these bundles, nothing else has changed so no change to tooling needed.
By 'old' firewall script do you mean the existing one in |
…ft/AzureTRE into damoo/1679-pipeline-substitution
…ft/AzureTRE into damoo/1679-pipeline-substitution
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.
Fantastico!! What a PR ❤️
/test-destroy-env |
Destroying PR test environment (RG: rg-tre4e00469a)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2527522640) |
Destroying branch test environment (RG: rg-trec7302e0e)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2527522640) |
Branch test environment destroy complete (RG: rg-trec7302e0e) |
PR test environment destroy complete (RG: rg-tre4e00469a) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2527629989 (with refid (in response to this comment from @damoodamoo) |
/test-shared-services |
🤖 pr-bot 🤖 🏃 Running shared service tests: https://github.com/microsoft/AzureTRE/actions/runs/2528324609 (with refid (in response to this comment from @damoodamoo) |
/test-shared_services |
🤖 pr-bot 🤖
You can use the following commands: (in response to this comment from @damoodamoo) |
Closes #1679
What is being addressed
This PR adds support for a template designer to update a secondary resource from a primary, using properties from the primary in the upgrade.
To do this, a designer can use the syntax
{{ resource.properties.prop_name }}
, which will be translated at runtime to the real value. Using this method, Nexus + Gitea (in this PR) now update the firewall as a secondary resource rather than directly via their own terraform. Since we have queueing in place it should mean that Gitea + Nexus can be deployed in parallel more safely.To support this the way outputs are returned from bundles into the cosmos object has been updated. Rather than converting every output to a string in the resource, we now allow a property bag to contain outputs of complex types.
In the UI, the notifications panel will show the pipeline steps such: