dc
d67a0e5d5f
Addresses both findings from the review of #408. runAutoDeploy was declared async after the service-pack step went, but calls createDatabase() and returns without awaiting anything. createDatabase() starts the request and reports through the component's own status flags rather than a returned promise, so there is nothing to await - drop the async rather than pretend to a contract the callee does not offer. runMakedataInNewWindow interpolated the context name, admin group and DC path straight into the query string. An ampersand in any of them started a new parameter and a space arrived truncated; a DC path containing a slash was only working because nothing decoded the query. Those three values are now percent-encoded at the build site, so the server reads back what the user chose. Tests: the new-window case now asserts the encoded forms, and a second case pins the values that need encoding (context with an ampersand and spaces, admin group with a space and a plus, DC path with a slash and a space). The deploy case no longer awaits a synchronous handler. Executed 24 of 24 SUCCESS (automatic + sasjs-configurator + deploy components).