apify actor:push-data inside an actor. The command is inside a dockerized shell script [1] and as simple as this:curl http://httpbin.org/ip | apify actor:push-data
2024-04-18T13:34:28.642Z at DatasetClient.throwOnNonExisting (/usr/local/lib/node_modules/apify-cli/node_modules/@crawlee/memory-storage/resource-clients/common/base-client.js:15:15) 2024-04-18T13:34:28.643Z at DatasetClient.pushItems (/usr/local/lib/node_modules/apify-cli/node_modules/@crawlee/memory-storage/resource-clients/dataset.js:158:18) 2024-04-18T13:34:28.644Z at async PushDataCommand.run (/usr/local/lib/node_modules/apify-cli/src/commands/actor/push-data.js:25:9) 2024-04-18T13:34:28.644Z at async PushDataCommand._run (/usr/local/lib/node_modules/apify-cli/node_modules/@oclif/command/lib/command.js:43:20) 2024-04-18T13:34:28.645Z at async Config.runCommand (/usr/local/lib/node_modules/apify-cli/node_modules/@oclif/config/lib/config.js:173:24) 2024-04-18T13:34:28.646Z at async Main.run (/usr/local/lib/node_modules/apify-cli/node_modules/@oclif/command/lib/main.js:28:9) 2024-04-18T13:34:28.647Z at async Main._run (/usr/local/lib/node_modules/apify-cli/node_modules/@oclif/command/lib/command.js:43:20) 2024-04-18T13:34:28.648Z at async /usr/local/lib/node_modules/apify-cli/src/bin/run:7:9
true and the cli then always uses the MemoryStorage regardless the ENV variables exposed by the Run for the Actor. If I overrode the forceCloud to true it uses the ApifyClient adaptor, it works as expected and I can see the data in the "Run Detail > Storage > Dataset" tab in the Apify Cloud Console. I'll file a Github Issue later and let's follow up there. Ok?