No data migration. Ploomber Cloud runs on AWS, and can integrate with your existing infrastructure such as S3, GCS, RedShift and Athena.

Ploomber

ploomber stores `.metadata`, they're prefixed with a dot so they're hidden by default, but you can see them with `ls -la` . that stores the task's last execution timestamp and source code. the rule to determine execution is either an upstream dependency has a higher timestamp or the source code has changed

you can run single tasks: `ploomber task {task-name}` . does that work? if you want to ignore status, you can force it with the `--force`  flag.

currently, there is no way to pass custom values to `--inject` so yeah you have to modify the env

Yes, I was using ploomber task but not with the --force flag!  I think it will do what I want. Thank you Eduardo! Ploomber is great!

awesome! feel free to ask any other questions

<@U03UR6Z9D27> are you using only ploomber or any other package? (`jupysql, sklearn-evaluation, ploomber-engine` )

The version has nothing to do with it, it exists since day one.

it's a leading dot with .metadata extension

but they are created after you run a task

so, I'm doing ls in the same level as pipeline.yaml, the only hidden files are: .gitignore and .ipynb_checkpoints

ah sorry, forgot to mention. they're stored next to your products

so if you store `products/stuff.csv` , it'll be `products/.stuff.metadata`

ooh, I get it now. Yes, I found them! Ok, now the problem is that the flag --force seems not to work

ahh, I know what is happening, Some part of the pipeline were run in a cluster. I only copied the products, not the metadata

yep, you need both so ploomber can recognize them

I'll add the metadata to the other piece of the pipeline and see what happens,  Thanks!