Using managed inputs¶
Info
Learn the concepts and fundamentals of managed inputs in the Explanation page.
Managed inputs are used to store and keep track of your inputs. They can be created either by referencing a prior run within your application, or by uploading new data. You can use managed inputs for runs as well as other features of the Nextmv Platform:
- Scenario tests: when creating a scenario test with the
nextmv cloud scenario createcommand, you can define scenarios using managed inputs as the data source. - Input sets: use them to create batch experiments or
scenario tests. When using the
nextmv cloud input-set createcommand, you can define one or more managed inputs to make up the input set.
Included in this how-to guide are instructions on how to interact with the
actions under the nextmv cloud managed-input command
tree. Go the reference section or use the --help option to see all the
available options for each command.
Create a managed input¶
Use the nextmv cloud managed-input create command to
create a new managed input for an application. Managed inputs can be create by
one of the following methods:
- From a run, by providing the
--run-idoption. - From a file (or directory) that is uploaded to Nextmv Cloud, by providing the
--upload-idoption.
To know which type of content format is expected for the
managed input, we recommend you specify the --content-format option.
Here is an example command that creates a json managed input from an
existing run ID.
If you have data in the filesystem that you want to upload as a managed input, there are a couple more steps to complete.
-
Create a new upload with the
nextmv cloud upload createcommand. -
The output contains an
upload_idand anupload_url. Let's use theupload_urlwith thenextmv cloud data uploadcommand to upload the actual data to Nextmv Cloud. This can be a file (json) or a directory (multi-file).
Once the data has been uploaded, we can create a managed input from it, by
using the upload_id that was returned when the upload was created.
⏳ Creating managed input...
{
"id": "managed-input-2b7g1bfy",
"name": "managed-input-2b7g1bfy",
"description": "",
"run_id": "",
"upload_id": "7a3ba4a9-a1ba-4a09-82fa-8942deae2d22",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T17:03:40.730434Z",
"updated_at": "2026-07-24T17:03:40.730434Z"
}
For multi-file, just set the --content-format option to
multi-file. When uploading data, provide a directory path to the --input
option.
The command above will create a random ID, and use the same identifier for the
managed input's name. The name of the managed input is used as a human-readable
You can use the --managed-input-id and/or --name options to
specify a custom ID and name for the managed input. For example:
⏳ Creating managed input...
{
"id": "baxter-burrow",
"name": "The managed input of Baxter's Burrow",
"description": "",
"run_id": "",
"upload_id": "7a3ba4a9-a1ba-4a09-82fa-8942deae2d22",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T17:06:30.178309Z",
"updated_at": "2026-07-24T17:06:30.178309Z"
}
Run with a managed input¶
Once a managed input has been created you can use it with the nextmv cloud run create
command by means of the --managed-input-id option. For example:
✅ Run latest-qMNuvtPDg created.
⏳ Getting run results...
💡 Removed assets from output for cleaner display, use --output to save the full output.
{
"description": "",
"id": "latest-qMNuvtPDg",
"metadata": {
"application_id": "uncanny-rodent",
"application_instance_id": "latest",
"application_version_id": "",
"created_at": "2026-07-24T17:08:23Z",
"duration": 6208.0,
"error": "",
"execution_class": "6c9500mb870s",
"execution_duration": 4992.0,
"format": {
"input": {
"type": "json"
},
"output": {
"type": "json"
}
},
"initiated_at": "2026-07-24T17:08:23.910772Z",
"input_size": 63.0,
"metrics": {
"message": "Hello, Patches",
"value": 1.23
},
"options": {
"active_options": {
"details": "true"
},
"options_summary": [
{
"name": "details",
"source": "version",
"value": "true"
}
]
},
"output_size": 25107.0,
"queuing_disabled": false,
"queuing_priority": 6,
"run_type": {
"type": "standard",
"definition_id": "",
"reference_id": ""
},
"runtime": "python-3_11",
"status_v2": "succeeded",
"tracking": {
"input_id": "baxter-burrow"
}
},
"name": "",
"user_email": "sebastian@nextmv.io",
"console_url": "https://cloud.nextmv.io/app/uncanny-rodent/run/latest-qMNuvtPDg?view=details",
"output": {
"options": {
"details": true
},
"solution": {
"message": "Hello, Patches"
},
"metrics": {
"value": 1.23,
"message": "Hello, Patches"
}
}
}
Get a managed input¶
Use the nextmv cloud managed-input get command to retrieve an existing
managed input for an application by its ID.
⏳ Getting managed input...
{
"id": "baxter-burrow",
"name": "The managed input of Baxter's Burrow",
"description": "",
"run_id": "",
"upload_id": "7a3ba4a9-a1ba-4a09-82fa-8942deae2d22",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T17:06:30.178309Z",
"updated_at": "2026-07-24T17:06:30.178309Z"
}
You can list all managed inputs in the application using the nextmv
cloud managed-input list command.
⏳ Listing managed inputs...
[
{
"id": "baxter-burrow",
"name": "The managed input of Baxter's Burrow",
"description": "",
"run_id": "",
"upload_id": "7a3ba4a9-a1ba-4a09-82fa-8942deae2d22",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T17:06:30.178309Z",
"updated_at": "2026-07-24T17:06:30.178309Z"
},
{
"id": "managed-input-2b7g1bfy",
"name": "managed-input-2b7g1bfy",
"description": "",
"run_id": "",
"upload_id": "7a3ba4a9-a1ba-4a09-82fa-8942deae2d22",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T17:03:40.730434Z",
"updated_at": "2026-07-24T17:03:40.730434Z"
},
{
"id": "managed-input-cveuuj71",
"name": "managed-input-cveuuj71",
"description": "",
"run_id": "latest-ltSESpPvR",
"upload_id": "",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T16:53:01.331114Z",
"updated_at": "2026-07-24T16:53:01.331114Z"
}
]
Update a managed input¶
You can update attributes of a managed input with the
nextmv cloud managed-input update command, such as its:
- Name
- Description
Please use the --help option on the nextmv cloud managed-input
update command to see all the available options
for updating a managed input. You cannot update the ID or actual input data. If
you need to change the data, you must create a new managed input.
⏳ Updating managed input...
✅ Managed input baxter-burrow updated successfully in application uncanny-rodent.
{
"id": "baxter-burrow",
"name": "This is an updated burrow for the Baxter managed input",
"description": "A brand new description for the Baxter managed input",
"run_id": "",
"upload_id": "7a3ba4a9-a1ba-4a09-82fa-8942deae2d22",
"format": {
"input": {
"type": "json"
}
},
"created_at": "2026-07-24T17:06:30.178309Z",
"updated_at": "2026-07-24T17:20:27.290859Z"
}
Delete a managed input¶
Warning
Deleting a managed input is irreversible. All the information associated with the managed input will be permanently deleted.
Delete a managed input using the nextmv cloud managed-input
delete command. The CLI will prompt you to confirm
deletion but you can override it with the --yes option.