Malformed JSON in test script parameters

[Steve Rydz]

When adding a test script that has parameters such as the "internet-connectivity" script, the value of the parameters key is not valid JSON.

See example: https://pastebin.canonical.com/p/3CJ4bw3tbk/

In this case the single quotes should be double quotes and booleans should not be capitalised. This makes it impossible to parse on the front-end therefore preventing it from allowing the user to add to the parameters via the UI.

[Lee Trager (ltrager)]

The UI should be looking at the interface field which contains the id of the interface. If one exists the the UI can map that id on the nose model.

The parameters field should not be used as it may not be current.

[Steve Rydz (steverydz)]

Sorry, I should have added the use case for this in the description. The use case is that we need to be able to supply a URL to a test script. If this isn't the way to do it what would you suggest instead?

[Lee Trager (ltrager)]

Apologies I misunderstood this bug, I thought this was for the ScriptResult model, not the Script model. You are correct that the websocket was incorrectly turning the parameters dictionary into a string. This has been fixed in the related branch.