Automate: Update the manifest refs to tags.

[prudhvigodithi]

Is your feature request related to a problem? Please describe

After every release the Post release activity is to update the manifest refs to point to the generated tags, here is an example manual PR .

Describe the solution you'd like

Have an jenkins jobs or extend existing jenkins job that cuts the tag for every component, followed by to raise a PR with updated manifest, where ref value inside the manifest points to the right tag.

Describe alternatives you've considered

No response

Additional context

No response

[dblock]

+1 on extending the existing job

[bbarani]

[Triage] We will work on auto updating the manifest with corresponding tag information after every release.

[hitenshKharva]

I would like to try fixing this issue.

[hitenshKharva]

@gaiksaya @peterzhuamazon I went through the approaches discussed during the office hours but I am still confused on the approach to fix this issue.
Few questions:

1. when a new release tag is generated, where should I fetch it?
2. My best case approach if we can run a python script via github action to replace manifest refs to tags? Does that sound good?
3. Also, if we go ahead with above approach what will be the optimal way to trigger the Github action once new tags are generated?

Thanks.

[gaiksaya]

Hey!

1. Release tags are generated after each release of OpenSearch. This is the workflow responsible for creating tags across all the repositories. Source coded here. This is the underlying library which is run in the above workflow.
2. There are 3 options:
   i. Create a new groovy library that will update the refs and create a pull request (all in one)
   ii. Create a python script that can be run on anything (jenkins/GHA)and then create pull request: Example
   iii. Create a simple GHA workflow that takes version as an input and does the update using it.
3. If using GitHub actions, it will be triggered using workflow_dispatch event that will take version as an input. Example: https://github.com/opensearch-project/data-prepper/blob/main/.github/workflows/release.yml#L3-L14. We can send dispatch as a post condition to above release-tag workflow.