Regression since OpenShift 3: it is no longer possible to input multiline template parameters

[webknjaz]

Hi, folks! I've migrated a template I used to have under OpenShift 3 to a new cluster running OpenShift 4 (https://openshift-console.osci.io). I'm facing a difference in the OpenShift Console Web UI that I can't seem to work around.
Some of my template parameters have to be multiline (in particular, a private key that ends up in a secret). In OS3 I used to go to the catalog, click on my template, and each <input> field in the configuration tab would have a double-sided arrow icon with a hint on hover saying “Expand to enter multiple lines of content. This is required if you need to include newline characters.”. I would click it and paste that private key with as many lines as necessary.

Now, in OS4, I can't find such expansion capability. It only allows one-line inputs for template parameters. Any chance I'm overlooking something? Is it a bug?

I've found an old ticket about OS3 from when that the original “expand” feature was implemented: https://bugzilla.redhat.com/show_bug.cgi?id=1312444#c4. The respective PR is openshift/origin-web-console#739.

The following screenshot demonstrates what I face in OS4:

The next screenshots are how it used to be implemented in OS3:

This is also filed @ https://issues.redhat.com/browse/OCPBUGS-23080.

[webknjaz]

The related input field seems to be coming from this place:

console/frontend/public/components/instantiate-template.tsx

Lines 295 to 305 in 802c16e

	<input
	type="text"
	className="pf-c-form-control"
	id={name}
	name={name}
	value={value}
	onChange={onParameterChanged}
	required={requiredInput}
	placeholder={placeholder}
	aria-describedby={helpID}
	/>

[webknjaz]

I also filed https://issues.redhat.com/browse/OCPBUGS-23080, not knowing what the best place for reporting is.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[webknjaz]

/remove-lifecycle rotten

[webknjaz]

/lifecycle frozen