[FR] Change docker publish flow to use release tag instead of latest tag

[blrchen]

Willingness to contribute

No. I cannot contribute a bug fix at this time.

Feature Request Proposal

Docker image publishing process change proposal

• For release branches, automatically publish docker image with corresponding release tag, e.g, feathr-registry:releases-v0.7.2
• Ensure deployment picks up latest released docker image, seems the easilest way to do this is link latest tag to LKG release tag.

Motivation

What is the use case for this feature?

No impact to end user experience. Only impacts deployment experience, this ask ensures correct registry docker image is used for deployment.

Details

No response

What component(s) does this feature request affect?

• Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
• Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
• Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
• Feature Registry Web UI: The Web UI for feature registry. Written in React