Skip to content

Handle CLI with input for local development without FileSystemStorage client #682

@Pijukatel

Description

@Pijukatel

When Apify CLI is used to run local actor with specific inputs, then it is creating specific file in specific kvs storage using FileSystemStorage client. If the actor is using different storage client, then such input is ignored.

Probably the Actor outside of Apify platform will have to try to read inputs using FileSystemStorage client even when it is using different storage clients. If such input exists, it should copy it over to whatever storage client it is using.

Maybe we should use APIFY_LOCAL_STORAGE_DIR to point to some temp location, create inputs there, in Actor we read input ASAP and copy them over to whatever storage client is set in the actor.

Open question: How should CLI behave if APIFY_LOCAL_STORAGE_DIR is already set? Should it respect it or override it

Metadata

Metadata

Assignees

No one assigned

    Labels

    t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions