Add Mesh page to OSSMC

[ferhoyos]

Describe the change

Add Mesh page to OSSMC

Bonus: Extract console plugin metadata into separate file, as indicated here: https://github.com/openshift/console/blob/master/frontend/packages/console-dynamic-plugin-sdk/README.md#plugin-metadata

Steps to test the PR

1. Click to Service Mesh / Mesh navigation menu
2. Verify that Kiali mesh page is loaded correctly

Automation testing

Cypress test to check that mesh page has been loaded correctly (detailed tests are included in Kiali repo)

Issue reference

Closes #308

[jmazzitelli]

During our build process, we have update this version string. Because it is now in a new file, we should make sure our build process doesn't break. I'm not sure exactly where we do this - it is either in the github workflow or in some Makefile. I will look to try to find it.

[jmazzitelli]

This looks like the place: https://github.com/kiali/openshift-servicemesh-plugin/blob/main/.github/workflows/release.yaml#L209

[jmazzitelli]

Note that we still need to change "version:" here in package.json (there is one at the top of the file)... but now we need to do this version update in this plugihn-metadata.ts file, too.

[jmazzitelli]

I think we want something similar to this:

        jq -r ".version |= \"${RELEASE_VERSION:1}\" plugin/package.json > plugin/package.json.tmp
        mv plugin/package.json.tmp plugin/package.json

        jq -r ".version |= \"${RELEASE_VERSION:1}\" plugin/plugin-metadata.json > plugin/plugin-metadata.json.tmp
        mv plugin/plugin-metadata.json.tmp plugin/plugin-metadata.json

But that probably isn't 100% correct because now the plugin version is inside a javascript file, not a json file so the "jq" tool likely will not work. So for that second set of commands we will need to use something like "sed" rather than "jq".

[jmazzitelli]

see ferhoyos#6

[jmazzitelli]

I created a PR to this PR so it updates the version strings properly in all the files where version string is now found (there is now a third file - plugin-metadata.ts - where version has to be updated by the release action).

See ferhoyos#6

You can test that the new script works by running it and checking the three files are correctly changed.

Try it with a snapshot version and non-snapshot version (the package.json and plugin-metadata.ts should not have -SNAPSHOT in the version string - the script will strip it out. The Makefile will still show -SNAPSHOT in the version string).

1. hack/update-version-string.sh v1.2.3 should result in:

diff --git a/Makefile b/Makefile
-VERSION ?= v1.85.0-SNAPSHOT
+VERSION ?= v1.2.3

diff --git a/plugin/package.json b/plugin/package.json
-  "version": "1.85.0",
+  "version": "1.2.3",

diff --git a/plugin/plugin-metadata.ts b/plugin/plugin-metadata.ts
-  version: '1.85.0',
+  version: '1.2.3',

2. hack/update-version-string.sh v1.2.3-SNAPSHOT should result in:

diff --git a/Makefile b/Makefile
-VERSION ?= v1.85.0-SNAPSHOT
+VERSION ?= v1.2.3-SNAPSHOT

diff --git a/plugin/package.json b/plugin/package.json
-  "version": "1.85.0",
+  "version": "1.2.3",

diff --git a/plugin/plugin-metadata.ts b/plugin/plugin-metadata.ts
-  version: '1.85.0',
+  version: '1.2.3',

my changes were added. now I'll now run this all and test it.

[jmazzitelli]

I can see the new Mesh option:

[jmazzitelli]

more changes needed for the release action so the new plugin-metadata.ts file gets updated in the release PRs that get generated.