Cloud Datum Stream Update¶
Make changes to an existing Cloud Datum Stream entity.
The changes to make can be provided by a combination of methods:
- Standard input, as a JSON object in the form supported by the Cloud Datum Stream update API.
- Command line options
- Command line parameter JSON object, including
@@file reference
For example, the following invocations produce equivalent results:
# using standard input
echo '{"enabled":false}' |s10k cloud-integrations datum-streams update --stream-id 100
# using parameter value
s10k cloud-integrations datum-streams update --stream-id 100 '{"enabled":false}'
# using parameter file reference - my-file.json contains {"enabled":false}
s10k cloud-integrations datum-streams update --stream-id 100 @@my-file.json
# using option
s10k cloud-integrations datum-streams update --stream-id 100 --disabled
The methods can be combined, with each method overriding settings duplicated in previous methods.
For example the following ends up changing the schedule to 300 because the command line parameter
overrides both the --schedule option and standard input values:
echo '{"schedule":900}' |s10k cloud-integrations datum-streams update --stream-id 100 \
--schedule 600 '{"schedule":300}'
Usage¶
s10k cloud-integrations datum-streams update
[-rI]
-stream=<datumStreamId>
[-S=<serviceIdentifier>]
[-m=<name>]
[-source=<sourceId>]
[-map=<mappingId>]
[-w=<schedule>]
[-prop=serviceProperty]...
[-node=<nodeId> | -loc=<locationId>]
[-e | -d]
[-mode=<displayMode>]
[<config>]
Tip
Use the --dry-run global option to preview the update,
without actually changing anything. For example:
s10k --dry-run cloud-integrations datum-streams update --stream-id 100 --disabled
Output¶
The updated datum stream (or a preview of the update if the --dry-run option was given).
Examples¶
s10k cloud-integrations datum-streams update --stream-id 100 --disabled
You can use c2c instead of cloud-integrations and ds instead of datum-streams:
s10k c2c ds update --stream-id 100 --disabled
+-----+----------------+-----------+---------+------+-----------+---------------------+----------------+------------+--------------------------------------------------------+
| ID | Name | Type | Enabled | Kind | Object ID | Source ID | Schedule | Mapping ID | Service Properties |
+-----+----------------+-----------+---------+------+-----------+---------------------+----------------+------------+--------------------------------------------------------+
| 100 | Big Solar Farm | SolarEdge | false | n | 123 | /BLD1/S1/R1/GEN/100 | 0 0/30 * * * * | 700 | { |
| | | | | | | /BLD1/S1/R1/INV/1 | | | "sourceIdMap" : { |
| | | | | | | | | | "/0000000/met/Production" : "/BLD1/S1/R1/GEN/100", |
| | | | | | | | | | "/0000000/inv/77777777-4E" : "/BLD1/S1/R1/INV/1" |
| | | | | | | | | | }, |
| | | | | | | | | | "placeholders" : { |
| | | | | | | | | | "siteId" : 0000000 |
| | | | | | | | | | } |
| | | | | | | | | | } |
+-----+----------------+-----------+---------+------+-----------+---------------------+----------------+------------+--------------------------------------------------------+
ID,Name,Type,Enabled,Kind,Object ID,Source ID,Schedule,Mapping ID,Service Properties
100,Big Solar Farm,SolarEdge,false,n,123,"/BLD1/S1/R1/GEN/100
/BLD1/S1/R1/INV/1",0 0/30 * * * *,700,"{
""sourceIdMap"" : {
""/0000000/met/Production"" : ""/BLD1/S1/R1/GEN/100"",
""/0000000/inv/77777777-4E"" : ""/BLD1/S1/R1/INV/1""
},
""placeholders"" : {
""siteId"" : 0000000
}
}"
[
{
"configId": 100,
"name": "Big Solar Farm",
"serviceIdentifier": "s10k.c2c.ds.solaredge.v1",
"created": "2025-02-26 11:21:31.409418Z",
"modified": "2026-07-22 00:33:26.638189Z",
"enabled": false,
"datumStreamMappingId": 700,
"schedule": "0 0/30 * * * *",
"kind": "n",
"objectId": 123,
"sourceId": "unused",
"serviceProperties": {
"sourceIdMap": {
"/0000000/met/Production": "/BLD1/S1/R1/GEN/100",
"/0000000/inv/77777777-4E": "/BLD1/S1/R1/INV/1"
},
"placeholders": {
"siteId": 0000000
}
}
}
]