You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should wait until we have the UI together to get an idea of what the inputs/API might look like, but an example would be:
xo start-deployment > deployment.json
xo transform \
--deployment=deployment.json \
--dest-schema=schema-params
NOTE: the deployment being returned from startDeployment will have the schemaName as a field alongside the params field. xo transform will take end-user params and the name of the schema the user submitted and run a mapper.js file in the embedded v8 engine to convert to the proper params for --dest-schema.
An example:
Using a guided config, we might ask about write throughput rather than RAM size for redis... but our main schema (schema-params.json) takes a "memory" parameter.
Add a command
xo transform
to transform input values between different different forms.Embedded v8 engines:
We should wait until we have the UI together to get an idea of what the inputs/API might look like, but an example would be:
xo start-deployment > deployment.json xo transform \ --deployment=deployment.json \ --dest-schema=schema-params
NOTE: the deployment being returned from startDeployment will have the
schemaName
as a field alongside theparams
field.xo transform
will take end-user params and the name of the schema the user submitted and run amapper.js
file in the embedded v8 engine to convert to the proper params for--dest-schema
.An example:
Using a guided config, we might ask about write throughput rather than RAM size for redis... but our main schema (schema-params.json) takes a "memory" parameter.
params-data.json
schema-params.json
A mapper.js file will be written by a bundle author:
mapper.js
The text was updated successfully, but these errors were encountered: