chore(v2): generate cache key and hash key

[capri-xiyue]

Description of your changes:
Fixed #5816, generate cache key and hash key

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[Bobgy]

Shall we move cache related code to a new cache folder? We will want to reuse them, and launcher already includes too much.

I feel a little reluctant for skipping unit testing. E.g. the unordered item issue is subtle and may be hard to catch.

[Bobgy]

Can this guarantee unordered items have a stable order? e.g. different input parameter names

[capri-xiyue]

The json package always orders keys when marshalling. Specifically:

1. Maps have their keys sorted lexicographically
2. Structs keys are marshalled in the order defined in the struct

FYI: https://stackoverflow.com/questions/18668652/how-to-produce-json-with-sorted-keys-in-go and https://golang.org/pkg/encoding/json/#Marshal.

[Bobgy]

FYI, you can use this executor input as reference

pipelines/v2/component/runtime_info_test.go

Line 234 in 039e8a6

want: &pipeline_spec.ExecutorInput{

[capri-xiyue]

Shall we move cache related code to a new cache folder? We will want to reuse them, and launcher already includes too much.

I feel a little reluctant for skipping unit testing. E.g. the unordered item issue is subtle and may be hard to catch.

The json marshall package handles the unordered item issue. I don't think we need UT for now to verify the functionality of json marshall package. In addition, same logic are used in KFP V1

pipelines/backend/src/cache/server/mutation.go

Line 223 in a44a225

func generateCacheKeyFromTemplate(template string) (string, error) {

.
I'm fine to add UT if we want to verify the logic of generate cacheKey struct based on the runtime info(adding a UT for this method

pipelines/v2/component/launcher.go

Line 496 in e43b0e8

func (l *Launcher) generateCacheKey(

)

[Bobgy]

/lgtm

[Bobgy]

/lgtm
/approve
Looks great!

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• v2/OWNERS [Bobgy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment