There are various places in the CLI where files can be read from and written to the user's file system. For example, reading files for a deploy, or writing output from an execute run, or cleaning the workflows folder when checking out.
Some of this IO is unbound: the CLI can read and write from any location on the user's system. This is a bit icky: to be a good digital citizen the CLI should really only read/write within a project root (or if there is no root, from the working folder).
We need to go through all these IO locations and put some kind of basic bounds on the valid paths.
TODO: I'll populate the list of all the places where the CLI can read/write files
There are various places in the CLI where files can be read from and written to the user's file system. For example, reading files for a deploy, or writing output from an execute run, or cleaning the
workflowsfolder when checking out.Some of this IO is unbound: the CLI can read and write from any location on the user's system. This is a bit icky: to be a good digital citizen the CLI should really only read/write within a project root (or if there is no root, from the working folder).
We need to go through all these IO locations and put some kind of basic bounds on the valid paths.
TODO: I'll populate the list of all the places where the CLI can read/write files