Azure mass archive

[Erica Neininger (ericaneininger)]

PR Summary

Code Reviewer: Pierre Siddall (@Pierre-siddall)

Update PostProc app to permit archive to the new Azure MASS system.

closes:#51

Code Quality Checklist

(Some checks are automatically carried out via the CI pipeline)

• I have performed a self-review of my own code
• My code follows the project's style guidelines
• Comments have been included that aid undertanding and enhance the
  readability of the code
• My changes generate no new warnings

Testing

• I have tested this change locally, using the Moci rose-stem suite
• [NA] If any tests fail (rose-stem or CI) the reason is understood and
  acceptable (eg. kgo changes)
• I have added tests to cover new functionality as appropriate (eg. system
  tests, unit tests, etc.)

rose-stem will only test the unit tests, as it does not push to MASS

I've also run a copy of the MOCI GAL test suite: u-dx886 with this branch

Test Suite Results - moci - TEST_moci53/run1

Suite Information

Item	Value
Suite Name	TEST_moci53/run1
Suite User	erica.neininger
Workflow Start	2026-05-05T13:53:14
Groups Run	postproc

Dependency	Reference	Main Like
moci	ericaneininger/moci@azure_mass_archive	False
SimSys_Scripts	MetOffice/SimSys_Scripts@main	True

Task Information

✅ succeeded tasks - 99

Security Considerations

• I have reviewed my changes for potential security issues
• Sensitive data is properly handled (if applicable)
• Authentication and authorisation are properly implemented (if applicable)

Performance Impact

• Performance of the code has been considered and, if applicable, suitable
  performance measurements have been conducted

AI Assistance and Attribution

• [NA] Some of the content of this change has been produced with the assistance
  of Generative AI tool name (e.g., Met Office Github Copilot Enterprise,
  Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the
  Simulation Systems AI policy
  (including attribution labels)

Documentation

• Where appropriate I have updated documentation related to this change and
  confirmed that it builds correctly

Code Review

• All dependencies have been resolved
• Related Issues have been properly linked and addressed
• CLA compliance has been confirmed
• Code quality standards have been met
• Tests are adequate and have passed
• Documentation is complete and accurate
• Security considerations have been addressed
• Performance impact is acceptable

[Erica Neininger (ericaneininger)]

OFFICIAL Thanks Jon, I've created the branch pp_gitrepo on your suite. I've also added your retrieve_massr change to my branch, so you can test both at the same time. I've run it as far as successfully installing the postproc app, so it should be good to go for you. The set up is a bit quick and dirty, just before you go copying this across lots of other suites ! You can run from a branch by checking out your suite, and then running the command "fcm switch pp_git_repo". Please be aware, that if you haven't used a suite pointing at the Git mirrors before, you will need to add the following to ~/.gitconfig on the relevant EX machine -

>>>>>

[url "cazcron2:/data/users/gitassist/git_mirrors/"]       insteadOf = localmirrors: [safe]       directory = /data/users/gitassist/git_mirrors/* [user]       email = ***@***.***       name = Jon Rostron <<<<<<< There are instructions for setting Git up properly ; locally here (but I think you'll get way with just the above): For info, particularly for Pierre 🙂 - here's the branch diff link on trac: https://code.metoffice.gov.uk/trac/roses-u/changeset?reponame=&new=355415%40d%2Fx%2F4%2F1%2F3%2Fpp_gitrepo&old=352940%40d%2Fx%2F4%2F1%2F3%2Ftrunk Thanks for testing this for me. Any issues, let me know. Erica

________________________________ From: Jon Seddon ***@***.***> Sent: Tuesday, May 12, 2026 15:28 To: MetOffice/moci ***@***.***> Cc: Erica Pearce ***@***.***>; Assign ***@***.***> Subject: Re: [MetOffice/moci] Azure mass archive (PR #53) @jonseddon commented on this pull request.

________________________________ In rose-meta/archive_and_meaning/postproc/HEAD/rose-meta.conf<#53 (comment)>:

=

=This option is fixed for the lifetime of a set and CANNOT be =changed retrospectively. ⬇️ Suggested change - = - =This option is fixed for the lifetime of a set and CANNOT be - =changed retrospectively. There's a new chres command and so the risk appetite can now be changed if required. — Reply to this email directly, view it on GitHub<#53 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZVSCA372FZWED3HQIIVNHD42MYHJAVCNFSM6AAAAACYRUCYCKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHM2DENZTGE2TSMZTGU>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were assigned.Message ID: ***@***.***> OFFICIAL

[Jon Seddon (jonseddon)]

Tested with Az-MASS in t-dx413/run2 and z-dx413/run1 for both values of risk appetite. Tested against moomin with m-dx413/run2 and confirmed that the changes don't affect the usage of moomin.