fix: revert namor upgrade

[tommartensen]

After #969 the UI was broken:

This PR reverts the change.

[rhacs-bot]

A single node development cluster (infra-pr-1084) was allocated in production infra for this PR.

CI will attempt to deploy us.gcr.io/stackrox-infra/infra-server:0.8.7-15-g77ecf9333c to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1084 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make install-local

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

[vjwilson]

@tommartensen
You don't have to revert this upgrade.
You could just update the option name that was deprecated to the new option.
https://github.com/jsonmaur/namor.js/blob/master/CHANGELOG.md#deprecations

Replace saltLength with salt

https://github.com/stackrox/infra/blob/master/ui/src/utils/cluster.utils.ts#L16-L17

[tommartensen]

@vjwilson thanks, unfortunately, the error does not go away, tested in #1085. Because master is currently broken, I would want to continue with the revert and open a new PR for the upgrade & fix.

[davdhacs]

👍