Update Gitea version and configuration for Azure Blob storage support. #4672

james-annages · 2025-09-12T15:28:16Z

Also had to change the bundle_runtime_image_build.sh to use buildx and force v2 manifests.

Resolves #4671

What is being addressed

Update the Verison of Gitea.
Change the storage over to be Azure blob not file share.
App servicse not happy loading a v1 manafest.

How is this addressed

bumped to verion of gitea in the docker file.
Removed all terraform code for the file share. repaced it with code for a blob container.
Updated bundle_runtime_image_build.sh to use buildx and manafests v2.

Also had to change the bundle_runtime_image_build.sh to use buildx and force v2 manifests.

james-annages · 2025-09-12T15:34:11Z

@jonnyry Have a look, should be fixed now 😄

marrobi · 2025-09-12T16:19:55Z

@james-annages do you know if it's possible to use managed identity rather than an access key? Access keys are blocked in all our subscriptions so can't test it out.

james-annages · 2025-09-12T16:36:33Z

@james-annages do you know if it's possible to use managed identity rather than an access key? Access keys are blocked in all our subscriptions so can't test it out.

@marrobi I dont think so. They are using the Azure go SDK but it looks like they have hardcoded using the key: Gitea Azure blob code

marrobi · 2025-10-03T11:01:52Z

@james-annages sorry its taken a while to get to this.

The breaking change - as I understand the data will not be "migrated"? If so we should use a major version bump as this requires a force parameter to be passed to the API.

james-annages · 2025-10-03T11:18:48Z

@james-annages sorry its taken a while to get to this.

The breaking change - as I understand the data will not be "migrated"? If so we should use a major version bump as this requires a force parameter to be passed to the API.

@marrobi Ye im happy to do so. The storage is not mirgated. People may be able to add the miration but i was not sure how to do so efectivlay.

github-actions · 2025-10-13T10:19:57Z

Unit Test Results

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

Results for commit 7726648.

♻️ This comment has been updated with latest results.

bumped the to account for the bracking change of the storage.

marrobi · 2025-10-13T10:39:09Z

@james-annages can you resolve this linting:

Run terraform fmt -check -recursive
templates/shared_services/gitea/terraform/gitea-webapp.tf
templates/workspace_services/gitea/terraform/gitea-webapp.tf
Error: Terraform exited with code 3.
Error: Process completed with exit code 1.

james-annages · 2025-10-13T11:23:57Z

@james-annages can you resolve this linting:

Run terraform fmt -check -recursive
templates/shared_services/gitea/terraform/gitea-webapp.tf
templates/workspace_services/gitea/terraform/gitea-webapp.tf
Error: Terraform exited with code 3.
Error: Process completed with exit code 1.

@marrobi sorted, sorry had missed the fail emails.

james-annages · 2025-10-13T11:42:26Z

/test

github-actions · 2025-10-13T11:42:38Z

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/18464649436 (with refid 8f2652f9)

(in response to this comment from @james-annages)

SvenAelterman · 2025-10-13T17:00:03Z

Is the only way to leverage Azure Blob from Gitea to use the storage account's access key? I am concerned that in 2025, we're still forced to use these access keys, which then require exemptions in many compliance policies.

james-annages · 2025-10-13T17:20:09Z

Is the only way to leverage Azure Blob from Gitea to use the storage account's access key? I am concerned that in 2025, we're still forced to use these access keys, which then require exemptions in many compliance policies.

@SvenAelterman I aggree, however the gitea code is using the Key in the Azure sdk and not giving options for other methords. Long term we can put a problem in with the gitea repo and see if they will make a change?

SvenAelterman · 2025-10-13T17:22:17Z

Long term we can put a problem in with the gitea repo and see if they will make a change?

I think that's a good idea. I perused the open issues at the Gitea repo and didn't see anything yet.

james-annages · 2025-10-14T15:45:40Z

Long term we can put a problem in with the gitea repo and see if they will make a change?

I think that's a good idea. I perused the open issues at the Gitea repo and didn't see anything yet.

Problem reased on the Gitea Github repo. Gitea repo issue

Copilot

Pull request overview

This PR updates the Gitea workspace and shared service templates to use a newer version of Gitea (1.24.5, up from 1.15/1.17.3) and migrates storage from Azure Files to Azure Blob Storage. The change also addresses compatibility issues with Azure App Service by updating the Docker build process to force v2 manifests using buildx.

Key changes:

Gitea version bumped to 1.24.5 across both workspace and shared service templates
Storage migrated from Azure Files (file share) to Azure Blob Storage (blob container)
Bundle versions updated to 2.0.1 (major version bump) reflecting the breaking storage migration
Docker build script updated to use buildx with platform specification for v2 manifest generation

Reviewed changes

Copilot reviewed 13 out of 14 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
templates/workspace_services/gitea/version.txt	Bumped version from 0.6.1 to 0.7.1 for the runtime image
templates/workspace_services/gitea/terraform/variables.tf	Removed unused `gitea_storage_limit` variable
templates/workspace_services/gitea/terraform/storage.tf	Replaced Azure Files share with Azure Blob container and updated private endpoint configuration
templates/workspace_services/gitea/terraform/gitea-webapp.tf	Added Azure Blob storage configuration environment variables, removed file share mount, updated dependencies
templates/workspace_services/gitea/terraform/data.tf	Changed DNS zone reference from file to blob storage
templates/workspace_services/gitea/terraform/.terraform.lock.hcl	Removed Terraform lock file
templates/workspace_services/gitea/porter.yaml	Bumped bundle version from 1.3.2 to 2.0.1
templates/workspace_services/gitea/docker/Dockerfile	Updated Gitea tag to 1.24.5 and added execute permission for configure script
templates/shared_services/gitea/terraform/gitea-webapp.tf	Migrated to Azure Blob storage configuration, removed file share mount and storage account block
templates/shared_services/gitea/porter.yaml	Bumped bundle version from 1.2.1 to 2.0.1
templates/shared_services/gitea/docker/version.txt	Bumped version from 0.3.12 to 0.4.1
templates/shared_services/gitea/docker/Dockerfile	Updated Gitea tag to 1.24.5
devops/scripts/bundle_runtime_image_build.sh	Updated to force buildx with amd64 platform and v2 manifests
CHANGELOG.md	Added breaking change notice for Gitea update and storage migration

Files not reviewed (1)

templates/workspace_services/gitea/terraform/.terraform.lock.hcl: Language not supported

Comments suppressed due to low confidence (1)

templates/workspace_services/gitea/terraform/.terraform.lock.hcl:1

The .terraform.lock.hcl file has been completely removed from the workspace services Gitea template, but it still exists in the shared services Gitea template (templates/shared_services/gitea/terraform/.terraform.lock.hcl). According to Terraform best practices, lock files should be checked into version control to ensure consistent provider versions across environments. This inconsistency should be addressed - either regenerate and include the lock file for workspace services or provide justification for its removal.

Copilot · 2025-11-24T08:53:33Z

devops/scripts/bundle_runtime_image_build.sh

+## Needed as workaround for v1 manifests not being supported in Azure App Service on Linux.
+


This comment appears incomplete. It should explain what the workaround is for and possibly link to a related issue. Consider completing it with details like: "Needed as workaround for v1 manifests not being supported in Azure App Service on Linux. BuildKit with buildx ensures v2 manifest generation."

Suggested change

## Needed as workaround for v1 manifests not being supported in Azure App Service on Linux.

## Workaround: Force BuildKit and buildx to ensure Docker produces v2 image manifests.

## Azure App Service on Linux does not support v1 image manifests, which are produced by the default Docker build.

## By using BuildKit with buildx (`DOCKER_BUILDKIT=1` and `docker buildx build`), we ensure v2 manifests are generated.

## See: https://github.com/microsoft/AzureTRE/issues/2532

Copilot · 2025-11-24T08:53:34Z

CHANGELOG.md

 <!-- markdownlint-disable MD041 -->
 ## 0.26.0 (Unreleased)
+**BREAKING CHANGES & MIGRATIONS**:
+* Updated the version of gitea and the runtime build script. Updating Gitea will remove the storage from underneath it and result in a redeploy. ([#4672](https://github.com/microsoft/AzureTRE/pull/4672))


According to the project's version management guidelines, component version updates should be documented in the CHANGELOG under a "COMPONENTS" section. This entry describes updates to Gitea (from 1.15/1.17.3 to 1.24.5) and bundle versions (workspace service: 1.3.2→2.0.1, shared service: 1.2.1→2.0.1). Consider adding a "COMPONENTS:" section after "BREAKING CHANGES & MIGRATIONS:" with the version updates formatted like:

COMPONENTS: * Update Gitea workspace service from 1.3.2 to 2.0.1 and Gitea version from 1.17.3 to 1.24.5 ([#4672](https://github.com/microsoft/AzureTRE/pull/4672)) * Update Gitea shared service from 1.2.1 to 2.0.1 and Gitea version from 1.15 to 1.24.5 ([#4672](https://github.com/microsoft/AzureTRE/pull/4672))

Shouldnt be under components but needs to be moved to latest release.

Update Gitea version and configuration for Azure Blob storage support.

2103f54

Also had to change the bundle_runtime_image_build.sh to use buildx and force v2 manifests.

github-actions bot added the external PR from an external contributor label Sep 12, 2025

james-annages added 2 commits September 12, 2025 15:31

updated change log.

0b93343

Merge branch 'microsoft:main' into gitea-update

eb0bd24

james-annages added 2 commits October 3, 2025 12:19

Merge branch 'main' into gitea-update

1c69b90

Merge branch 'main' into gitea-update

455213b

james-annages requested a review from a team as a code owner October 13, 2025 10:18

james-annages added 2 commits October 13, 2025 11:21

Bump Gitea shared service version to 2.0.1

93ee39b

bumped the to account for the bracking change of the storage.

Bump Gitea workspace service version to 2.0.1

099c453

bumped the to account for the bracking change of the storage.

james-annages added 3 commits October 13, 2025 10:54

fixed the Metrics tag in the terraform code.

9fc028a

fixed teraform linting

f026417

fixing the Terraform valadation error.

7726648

james-annages requested review from JC-wk and marrobi October 13, 2025 11:28

james-annages self-assigned this Oct 13, 2025

marrobi requested a review from Copilot November 24, 2025 08:48

Copilot started reviewing on behalf of marrobi November 24, 2025 08:48 View session

Copilot finished reviewing on behalf of marrobi November 24, 2025 08:53

Copilot AI reviewed Nov 24, 2025

View reviewed changes

		## Needed as workaround for v1 manifests not being supported in Azure App Service on Linux.

-## Needed as workaround for v1 manifests not being supported in Azure App Service on Linux.
+## Workaround: Force BuildKit and buildx to ensure Docker produces v2 image manifests.
+## Azure App Service on Linux does not support v1 image manifests, which are produced by the default Docker build.
+## By using BuildKit with buildx (`DOCKER_BUILDKIT=1` and `docker buildx build`), we ensure v2 manifests are generated.
+## See: https://github.com/microsoft/AzureTRE/issues/2532

Update Gitea version and configuration for Azure Blob storage support. #4672

Are you sure you want to change the base?

Update Gitea version and configuration for Azure Blob storage support. #4672

Uh oh!

Conversation

james-annages commented Sep 12, 2025

Resolves #4671

What is being addressed

How is this addressed

Uh oh!

james-annages commented Sep 12, 2025

Uh oh!

marrobi commented Sep 12, 2025

Uh oh!

james-annages commented Sep 12, 2025

Uh oh!

marrobi commented Oct 3, 2025

Uh oh!

james-annages commented Oct 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Oct 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Unit Test Results

Uh oh!

marrobi commented Oct 13, 2025

Uh oh!

james-annages commented Oct 13, 2025

Uh oh!

james-annages commented Oct 13, 2025

Uh oh!

github-actions bot commented Oct 13, 2025

Uh oh!

SvenAelterman commented Oct 13, 2025

Uh oh!

james-annages commented Oct 13, 2025

Uh oh!

SvenAelterman commented Oct 13, 2025

Uh oh!

james-annages commented Oct 14, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

marrobi Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

marrobi Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

james-annages commented Oct 3, 2025 •

edited

Loading

github-actions bot commented Oct 13, 2025 •

edited

Loading