Query Language stays locked to openCypher after unchecking IAM on a Neptune Analytics connection

[kmcginnes]

Description

In the connection form, choosing Service Type "Neptune Analytics" forces Query Language to openCypher and disables the Query Language select. If the user then unchecks "AWS IAM Auth Enabled", the Service Type select disappears but serviceType keeps the value neptune-graph. Query Language stays locked to openCypher, and the control that locked it is no longer on screen, so there's no way to see why or to undo it without re-checking IAM.

In packages/graph-explorer/src/modules/CreateConnection/CreateConnection.tsx:

• onFormChange sets queryEngine: "openCypher" when serviceType becomes "neptune-graph".
• The Query Language select is disabled={form.serviceType === "neptune-graph"}. It doesn't check whether IAM is still enabled.

Environment

• Browser: any
• Graph Explorer Version: current main
• Graph Database & Version: any

Steps to Reproduce

1. Open Create Connection.
2. Check "AWS IAM Auth Enabled". On main this also needs "Using Proxy-Server".
3. Set Service Type to "Neptune Analytics". Query Language switches to openCypher and is disabled.
4. Uncheck "AWS IAM Auth Enabled".
5. See that Query Language is still disabled and set to openCypher, with no Service Type control visible.

Expected Behavior

Unchecking IAM gives the user back control of Query Language. I see two ways to do it:

• Reset serviceType to "neptune-db" when IAM is unchecked.
• Change the lock condition to awsAuthEnabled && serviceType === "neptune-graph", so the saved serviceType doesn't matter while IAM is off.

Either way, add a form test for this sequence.

Related Issues

• Only create an openCypher connection for Neptune Analytics #1021 is about the Neptune Analytics connection defaults on notebooks. It's related to this but not the same problem.

Important

Internal only — this issue is maintained by the core team and is not accepting external contributions.