Description

Frontend counterpart to #16669

Only planned frontend contribution in support of process baselines feature.

Discussed details with Jouko in Slack thread.

Surprises and Residue

1. Selection did not work until I added exception in onChange function.

   The if statement looks dubious.

2. During debugging, I temporarily added Cluster type to newClusterDefault and was able to improve it, but:

   • It lacks some properties that seem irrelevant to manifest installation, but deserve clearer thinking whether to use TypeScript Omit type utility.
     https://www.typescriptlang.org/docs/handbook/utility-types.html#omittype-keys

   • Investigation of TypeScript errors is prerequisite to add | null to some properties of Cluster type.

User-facing documentation

• CHANGELOG.md update is not needed
• documentation PR is not needed

Testing and quality

• the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
• CI results are inspected

Automated testing

• added unit tests
• added e2e tests
• added regression tests
• added compatibility tests
• modified existing tests

How I validated my change

1. npm run tsc in ui/apps/platform folder
2. npm run lint:fast-dev in ui/apps/platform folder
3. npm run start in ui/apps/platform folder with staging demo as central

Manual testing

1. Visit /main/clusters and click link to visit cluster page

   • With 'ROX_AUTOLOCK_PROCESS_BASELINES' feature flag disabled, see absence of Automatically lock process baselines selection.
     

   • With 'ROX_AUTOLOCK_PROCESS_BASELINES' feature flag enabled via temporary code change, see presence of Automatically lock process baselines selection Disabled when autoLockProcessBaselinesConfig: null in cluster response.
     

     For manifest installation method, see Automatically lock process baselines selection itself is enabled, and select Enable to see property set in form values via temporary JSON.stringify in console.log statement.