Change the way "inherited" workspaces retrieve the base workspace code

[jonnyry]

Resolves #4162

What is being addressed

Change the way inherited workspaces retrieve the base workspace code - see solution description in #4162

Notes

1. Currently requires the 'canary' release of porter. Ideally this should be a pinned version, however we are waiting for a new version release which includes the --build-context parameter.
(Now resolved - Porter have release version v1.2.1 incorporating the change.)

[github-actions]

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 177c97d.

♻️ This comment has been updated with latest results.

[tim-p-allen]

so do you need to have built base first? Will it just use the latest version of base?

[jonnyry]

so do you need to have built base first? Will it just use the latest version of base?

you don't need to have base built first, it pulls the latest files from the ../base directory, by using the 'base' --build-context passed to porter build.

[tim-p-allen]

so do you need to have built base first? Will it just use the latest version of base?

you don't need to have base built first, it pulls the latest files from the ../base directory, by using the 'base' --build-context passed to porter build.

Ahh got you. Nice. Happy to approve will test later

[tim-p-allen]

/test f6255a6

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12306981977 (with refid bc30f232)

(in response to this comment from @tim-allen-ck)

[tim-p-allen]

@jonnyry https://github.com/microsoft/AzureTRE/actions/runs/12306981977/job/34350005999#step:3:1

[jonnyry]

@jonnyry https://github.com/microsoft/AzureTRE/actions/runs/12306981977/job/34350005999#step:3:1

Ah let me take a look.

[jonnyry]

/test 8475e2a

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12314479660 (with refid bc30f232)

(in response to this comment from @jonnyry)

[jonnyry]

/test 43d4a60

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12314638144 (with refid bc30f232)

(in response to this comment from @jonnyry)

[jonnyry]

Made a change so that the porter build --build-context parameter is only used when required, i.e. for the following workspaces:

• airlock-import-review
• unrestricted

In all other cases, the --build-context parameter is not used.

The bundle-build make target does this by looking for a file named porter-build-context.env in the workspace folder, if it exists, it grabs the additional build context from the file and passes it to porter build, else it runs porter build without the parameter.

[jonnyry]

@jonnyry think we need to wait for a new Porter release for this? Not sure running on canary is wise given it could "update" at any time.

Yes indeed. I have requested a patch release, though I don't think its quite as quick and simple as a release of the mixins - they are discussing and will get back to me.

[jonnyry]

Porter have released version v1.2.1 incorporating the change. https://github.com/getporter/porter/releases/tag/v1.2.1

[jonnyry]

/test 184b000

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12458499867 (with refid bc30f232)

(in response to this comment from @jonnyry)

[jonnyry]

/test-destroy-env

[github-actions]

Destroying PR test environment (RG: rg-trebc30f232)... (run: https://github.com/microsoft/AzureTRE/actions/runs/12463669373)

[github-actions]

PR test environment destroy complete (RG: rg-trebc30f232)

[jonnyry]

/test 184b000

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12464141375 (with refid bc30f232)

(in response to this comment from @jonnyry)

[marrobi]

As long as tested to work, looks great. Thanks again!

[jonnyry]

/test 177c97d

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12471249205 (with refid bc30f232)

(in response to this comment from @jonnyry)