From ec52ed405557f5af5f1c2830a45b5ef2c84def6c Mon Sep 17 00:00:00 2001 From: vincent Date: Sun, 13 Dec 2020 14:04:57 +0100 Subject: [PATCH] update readme --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2d391f4..f9638a7 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ See the full example [here](https://github.com/vincentclaes/datajob/tree/main/ex [task1, task2] >> task3 -## Deploy example +## Deploy and destroy Deploy your pipeline using a unique identifier `--stage` and point to the configuration of the pipeline using `--config` @@ -64,14 +64,17 @@ Deploy your pipeline using a unique identifier `--stage` and point to the config export AWS_PROFILE=my-profile cd examples/data_pipeline_simple datajob deploy --stage dev --config datajob_stack.py + datajob destroy --stage dev --config datajob_stack.py -> Note: When using datajob cli to deploy your pipline, we shell out to aws cdk. + +> Note: When using datajob cli to deploy a pipeline, we shell out to aws cdk. > You can circumvent shelling out to aws cdk by running `cdk` explicitly. > datajob cli prints out the commands it uses in the back to build the pipeline. > If you want, you can use those. cd examples/data_pipeline_simple cdk deploy --app "python datajob_stack.py" -c stage=dev + cdk destroy --app "python datajob_stack.py" -c stage=dev # Ideas