Deploy new yaml file generation feature

[ljwh2]

Deploy without SLURM migration changes in first instance

[karatugo]

My Plan for this task

• [x] Rollback Changes in dev and master:

  • Checkout to dev branch: git checkout dev.
  • Create a backup branch: git branch backup_dev.
  • git reset --hard 80437fd6dff05c855063af597d27d568e229219c to rollback to this commit https://github.com/EBISPOT/gwas-sumstats-service/commit/80437fd6dff05c855063af597d27d568e229219c
  • Repeat these steps for the master branch.

• [x] Cherry pick changes to dev:

  • git checkout dev.
  • Cherry pick: git cherry-pick 7847851 bb3ddb7.

• [x] Test in sandbox:

  • Conduct our tests.

• [x] Merge dev to master:

  • Checkout to master: git checkout master.
  • Merge dev: git merge dev.

• [x] Tag release in master

  • git tag v1.3.9
  • git push origin v1.3.9

• [x] Briefly test in prod:

  • Make sure that everything is up and running

• [x] Merge Rolled Back Changes to dev:

  • Manually re-apply the changes in backup_dev.

[karatugo]

Test OK in sandbox.

[karatugo]

Merged dev to master. https://github.com/EBISPOT/gwas-sumstats-service/pull/284

[karatugo]

Created tag v1.3.9 https://github.com/EBISPOT/gwas-sumstats-service/releases/tag/v1.3.9

[karatugo]

Published the release v1.3.9. https://github.com/EBISPOT/gwas-sumstats-service/releases/tag/v1.3.9

[karatugo]

Released to prod now. https://gitlab.ebi.ac.uk/gwas/gwas-sumstats-service/-/pipelines/485458

[jiyue1214]

I confirm that yaml files for the new submission are in the new format. I will suggest closing this ticket.