diff --git a/1.8/404.html b/1.8/404.html index 16a26b5..004f01f 100644 --- a/1.8/404.html +++ b/1.8/404.html @@ -1 +1 @@ - DaaC from dbt artifacts

404 - Not found

\ No newline at end of file + DaaC from dbt artifacts

404 - Not found

\ No newline at end of file diff --git a/1.8/index.html b/1.8/index.html index 4a1c1db..88bb74f 100644 --- a/1.8/index.html +++ b/1.8/index.html @@ -1,4 +1,4 @@ - dbterd - DaaC from dbt artifacts
Skip to content

dbterd

CLI to generate Diagram-as-a-code file (DBML, Mermaid, PlantUML, GraphViz, D2) from dbt artifact files (required: dbt dbt)

PyPI version python-cli License: MIT python codecov

pip install dbterd --upgrade Successfully installed dbterd restart ↻

Verify installation:

dbterd --version
+ dbterd - DaaC from dbt artifacts      
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
dbterd
 
CLI to generate Diagram-as-a-code file (DBML, Mermaid, PlantUML, GraphViz, D2) from dbt artifact files (required: dbt dbt)
 
PyPI version python-cli License: MIT python codecov
 
 pip install dbterd --upgrade  Successfully installed dbterd restart ↻ 
 
Verify installation:
 
dbterd --version
 
 
Quick examine with existing samples
 
 Click me 
# select all models in dbt_resto
 dbterd run -ad samples/dbtresto
 # select all models in dbt_resto, Select multiple dbt resources
diff --git a/1.8/license.html b/1.8/license.html
index 12ea55e..3fb1ca9 100644
--- a/1.8/license.html
+++ b/1.8/license.html
@@ -1 +1 @@
- License - DaaC from dbt artifacts     
 
 
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
License
 
MIT License
 
Copyright © 2022 Dat Nguyen
 
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  
 
  
  
  
 
 
 
         
\ No newline at end of file
+ License - DaaC from dbt artifacts     
 
 
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
License
 
MIT License
 
Copyright © 2022 Dat Nguyen
 
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  
 
  
  
  
 
 
 
         
\ No newline at end of file
diff --git a/1.8/nav/development/CHANGELOG.html b/1.8/nav/development/CHANGELOG.html
index 71a5095..4f6e672 100644
--- a/1.8/nav/development/CHANGELOG.html
+++ b/1.8/nav/development/CHANGELOG.html
@@ -1 +1 @@
- Change Log - DaaC from dbt artifacts     
 
 
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
Change Log
 
Check the Github Releases out!
  
 
  
  
  
 
 
 
         
\ No newline at end of file
+ Change Log - DaaC from dbt artifacts     
 
 
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
Change Log
 
Check the Github Releases out!
  
 
  
  
  
 
 
 
         
\ No newline at end of file
diff --git a/1.8/nav/development/contributing-guide.html b/1.8/nav/development/contributing-guide.html
index 1b2ab5c..400d891 100644
--- a/1.8/nav/development/contributing-guide.html
+++ b/1.8/nav/development/contributing-guide.html
@@ -1,4 +1,4 @@
- Contribution Guideline - DaaC from dbt artifacts      
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
Contributing to dbterd
 
dbterd is open source software. It is what it is today because community members have opened issues, provided feedback, and contributed to the knowledge loop. Whether you are a seasoned open source contributor or a first-time committer, we welcome and encourage you to contribute code, documentation, ideas, or problem statements to this project.
 
     
  1. About this document
    2.  
  2. Getting the code
    3.  
  3. Setting up an environment
    4.  
  4. Testing dbterd
    5.  
  5. Submitting a Pull Request
    6.  
 
About this document
 
There are many ways to contribute to the ongoing development of dbterd, such as by participating in discussions and issues. We encourage you to first read our higher-level document: "Expectations for Open Source Contributors".
 
The rest of this document serves as a more granular guide for contributing code changes to dbterd (this repository). It is not intended as a guide for using dbterd, and some pieces assume a level of familiarity with Python development with poetry. Specific code snippets in this guide assume you are using macOS or Linux and are comfortable with the command line.
 
     
  • Branches: All pull requests from community contributors should target the main branch (default). If the change is needed as a patch for a minor version of dbt that has already been released (or is already a release candidate), a maintainer will backport the changes in your PR to the relevant "latest" release branch (1.0.<latest>, 1.1.<latest>, ...). If an issue fix applies to a release branch, that fix should be first committed to the development branch and then to the release branch (rarely release-branch fixes may not apply to main).
    •  
  • Releases: Before releasing a new minor version, we prepare a series of beta release candidates to allow users to test the new version in live environments. This is an important quality assurance step, as it exposes the new code to a wide variety of complicated deployments and can surface bugs before official release. Releases are accessible via pip.
    •  
 
Getting the code
 
Installing git
 
You will need git in order to download and modify the dbterd source code. On macOS, the best way to download git is to just install Xcode.
 
External contributors
 
You can contribute to dbterd by forking the dbterd repository. For a detailed overview on forking, check out the GitHub docs on forking. In short, you will need to:
 
     
  1. Fork the dbterd repository
    2.  
  2. Clone your fork locally
    3.  
  3. Check out a new branch for your proposed changes
    4.  
  4. Push changes to your fork
    5.  
  5. Open a pull request against datnguye/dbterd from your forked repository
    6.  
 
Setting up an environment
 
There are some tools that will be helpful to you in developing locally. While this is the list relevant for dbterd development, many of these tools are used commonly across open-source python projects.
 
Tools
 
We will buy poetry in dbterd development and testing.
 
So first install poetry via pip: 
python3 -m pip install poetry --upgrade
+ Contribution Guideline - DaaC from dbt artifacts      
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
Contributing to dbterd
 
dbterd is open source software. It is what it is today because community members have opened issues, provided feedback, and contributed to the knowledge loop. Whether you are a seasoned open source contributor or a first-time committer, we welcome and encourage you to contribute code, documentation, ideas, or problem statements to this project.
 
     
  1. About this document
    2.  
  2. Getting the code
    3.  
  3. Setting up an environment
    4.  
  4. Testing dbterd
    5.  
  5. Submitting a Pull Request
    6.  
 
About this document
 
There are many ways to contribute to the ongoing development of dbterd, such as by participating in discussions and issues. We encourage you to first read our higher-level document: "Expectations for Open Source Contributors".
 
The rest of this document serves as a more granular guide for contributing code changes to dbterd (this repository). It is not intended as a guide for using dbterd, and some pieces assume a level of familiarity with Python development with poetry. Specific code snippets in this guide assume you are using macOS or Linux and are comfortable with the command line.
 
     
  • Branches: All pull requests from community contributors should target the main branch (default). If the change is needed as a patch for a minor version of dbt that has already been released (or is already a release candidate), a maintainer will backport the changes in your PR to the relevant "latest" release branch (1.0.<latest>, 1.1.<latest>, ...). If an issue fix applies to a release branch, that fix should be first committed to the development branch and then to the release branch (rarely release-branch fixes may not apply to main).
    •  
  • Releases: Before releasing a new minor version, we prepare a series of beta release candidates to allow users to test the new version in live environments. This is an important quality assurance step, as it exposes the new code to a wide variety of complicated deployments and can surface bugs before official release. Releases are accessible via pip.
    •  
 
Getting the code
 
Installing git
 
You will need git in order to download and modify the dbterd source code. On macOS, the best way to download git is to just install Xcode.
 
External contributors
 
You can contribute to dbterd by forking the dbterd repository. For a detailed overview on forking, check out the GitHub docs on forking. In short, you will need to:
 
     
  1. Fork the dbterd repository
    2.  
  2. Clone your fork locally
    3.  
  3. Check out a new branch for your proposed changes
    4.  
  4. Push changes to your fork
    5.  
  5. Open a pull request against datnguye/dbterd from your forked repository
    6.  
 
Setting up an environment
 
There are some tools that will be helpful to you in developing locally. While this is the list relevant for dbterd development, many of these tools are used commonly across open-source python projects.
 
Tools
 
We will buy poetry in dbterd development and testing.
 
So first install poetry via pip: 
python3 -m pip install poetry --upgrade
 
 
then, start installing the local environment: 
python3 -m poetry install
 python3 -m poetry shell
 poe git-hooks
diff --git a/1.8/nav/guide/cli-references.html b/1.8/nav/guide/cli-references.html
index d8060d3..8c6cab7 100644
--- a/1.8/nav/guide/cli-references.html
+++ b/1.8/nav/guide/cli-references.html
@@ -1,4 +1,4 @@
- CLI Reference - DaaC from dbt artifacts      
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
CLI Reference (dbterd)
 
Run dbterd --help or dbterd -h to see the basic guideline for CLI Reference
 
 dbterd -h Usage: dbterd [OPTIONS] COMMAND [ARGS]...
 
 Tools for producing diagram-as-code
 
 Options:
 --version Show the version and exit.
 -h, --help Show this message and exit.
 
 Commands:
 debug Inspect the hidden magics
 run Run the convert
  
 
dbterd run
 
Command to generate diagram-as-a-code file
 
Examples:
 
 
 
 
dbt docs generate
+ CLI Reference - DaaC from dbt artifacts      
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
CLI Reference (dbterd)
 
Run dbterd --help or dbterd -h to see the basic guideline for CLI Reference
 
 dbterd -h Usage: dbterd [OPTIONS] COMMAND [ARGS]...
 
 Tools for producing diagram-as-code
 
 Options:
 --version Show the version and exit.
 -h, --help Show this message and exit.
 
 Commands:
 debug Inspect the hidden magics
 run Run the convert
  
 
dbterd run
 
Command to generate diagram-as-a-code file
 
Examples:
 
 
 
 
dbt docs generate
 dbterd run [-t dbml or -t mermaid]
 
 
 
 
Usage: dbterd run [OPTIONS]
 
diff --git a/1.8/nav/guide/dbt-cloud/download-artifact-from-a-job-run.html b/1.8/nav/guide/dbt-cloud/download-artifact-from-a-job-run.html
index 6656612..ddfb243 100644
--- a/1.8/nav/guide/dbt-cloud/download-artifact-from-a-job-run.html
+++ b/1.8/nav/guide/dbt-cloud/download-artifact-from-a-job-run.html
@@ -1,4 +1,4 @@
- Download artifacts from a Job Run - DaaC from dbt artifacts      
 
  
  
 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
Download artifacts from a Job Run
 
This is a guideline on how to download manifest.json and catalog.json from a Job Run by using dbt CLoud Administrative API, under the Retrieve Run Artifact endpoint. Therefore, we don't need to run dbt docs generate locally anymore.
 
In order to support dbt Cloud users, dbterd is now having multiple CLI options starting with --dbt-cloud to let us configure the connection to the complete dbt Cloud Job Run.
 
 
Prerequisites
 
     
  • You have a dbt Cloud account with Team and Enterprise plans 💰
    •  
  •  
    You have a job or go create a new job with a single step 🏃
     
    dbt docs generate
+ Download artifacts from a Job Run - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Download artifacts from a Job Run
     
    This is a guideline on how to download manifest.json and catalog.json from a Job Run by using dbt CLoud Administrative API, under the Retrieve Run Artifact endpoint. Therefore, we don't need to run dbt docs generate locally anymore.
     
    In order to support dbt Cloud users, dbterd is now having multiple CLI options starting with --dbt-cloud to let us configure the connection to the complete dbt Cloud Job Run.
     
     
    Prerequisites
     
       
    • You have a dbt Cloud account with Team and Enterprise plans 💰
      •  
    •  
      You have a job or go create a new job with a single step 🏃
       
      dbt docs generate
 
       
      •  
    •  
      Make sure that you have at least 1 successful run ✅
       
      •  
     
     
    1. Prepare the environment variables
     
    Behind the scene, the API Endpoint will look like: https://{host_url}/api/{api_version}/accounts/{account_id}/runs/{run_id}/artifacts/{path}.
     
    And the dbt Cloud's Job Rub will have the URL constructed as https://<host_url>/deploy/<account_id>/projects/irrelevant/runs/<run_id>.
     
    In the above:
     
      
     URL Part Environment Variable CLI Option Description 
           
     host_url DBTERD_DBT_CLOUD_HOST_URL --dbt-cloud-host-url Host URL, also known as Access URL (Default to cloud.getdbt.com) 
     
     account_id DBTERD_DBT_CLOUD_ACCOUNT_ID --dbt-cloud-account-id dbt Cloud Account ID 
     
     run_id DBTERD_DBT_CLOUD_RUN_ID --dbt-cloud-run-id dbt Cloud successful job run ID 
     
     api_version DBTERD_DBT_CLOUD_API_VERSION --dbt-cloud-api-version dbt Cloud API version (Default to v2) 
     
     path N/A N/A Artifact relative file path. You don't need to care about this part as dbterd managed it already 
          
     
    Besides, we need another one which is very important, the service token:
     
       
    • Go to Account settings / Service tokens. Click + New token
      •  
    • Enter Service token name e.g. "ST_dbterd"
      •  
    • Click Add and select Job Admin permission. Optionally, select the right project or all by default
      •  
    • Click Save
      •  
    • Copy token & Pass it to the Environment Variable (DBTERD_DBT_CLOUD_SERVICE_TOKEN) or the CLI Option (--dbt-cloud-service-token)
      •  
     
    Finally, fill in your_value and execute the (Linux or Macos) command below:
     
    export DBTERD_DBT_CLOUD_SERVICE_TOKEN=your_value
 export DBTERD_DBT_CLOUD_HOST_URL=your_value
 export DBTERD_DBT_CLOUD_ACCOUNT_ID=your_value
diff --git a/1.8/nav/guide/targets/generate-d2.html b/1.8/nav/guide/targets/generate-d2.html
index 59fac2a..b453484 100644
--- a/1.8/nav/guide/targets/generate-d2.html
+++ b/1.8/nav/guide/targets/generate-d2.html
@@ -1,4 +1,4 @@
- D2 - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate D2 ERD
     
    1. Install D2 CLI
     
    # With --dry-run the install script will print the commands it will use
+ D2 - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate D2 ERD
     
    1. Install D2 CLI
     
    # With --dry-run the install script will print the commands it will use
 # to install without actually installing so you know what it's going to do.
 curl -fsSL https://d2lang.com/install.sh | sh -s -- --dry-run
 # If things look good, install for real.
diff --git a/1.8/nav/guide/targets/generate-dbml.html b/1.8/nav/guide/targets/generate-dbml.html
index d927774..96d9c97 100644
--- a/1.8/nav/guide/targets/generate-dbml.html
+++ b/1.8/nav/guide/targets/generate-dbml.html
@@ -1 +1 @@
- DBML - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate DBML
     
    1. Produce your manifest json
     
    In your dbt project (I am using dbt-resto/integration_tests for demo purpose), try to build the docs:
     
     dbt docs generate 01:40:58 Running with dbt=1.3.4 01:40:58 Partial parse save file not found. Starting full parse. 01:41:00 Found 0 models, 0 tests, 0 snapshots, 0 analyses, 356 macros, 1 operation, 0 seed files, 0 sources, 0 exposures, 0 metrics 01:41:00  01:41:00 Concurrency: 4 threads (target='postgres') 01:41:00  01:41:00 Done. 01:41:00 Building catalog 01:41:00 Catalog written to .\target\catalog.json 
     
    2. Generate DBML
     
    Copy manifest.json and catalog.json into a specific folder OR do nothing and let's assume we're using dbt/target directory, and run
     
     
    Sample Usage
     
    dbterd run -ad "/path/to/dbt/target" -o "/path/to/output"
     
     
     dbterd run -ad "samples/dbtresto" -s model.dbt_resto 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.dbml (base.py:75) 
     
    File ./target/output.dbml will be generated as the result
     
    3. Build database docs site (Optional)
     
    Assuming you're already familiar with dbdocs
     
     
    Sample Usage
     
    dbdocs build "/path/to/output/output.dbml"
     
     
     dbdocs build "./target/output.dbml" √ Parsing file content ? Project name: poc ‼ Password is not set for 'poc' √ Done. Visit: https://dbdocs.io/datnguye/poc 
     
    The site will be looks like:
     
    screencapture-dbdocs-io-datnguye-poc-2022-12-18-22_02_28.png
     
    Result after applied Model Selection: screencapture-dbdocs-io-datnguye-poc-2023-02-25-10_29_32.png
      
     
      
      
      
     
     
     
             
\ No newline at end of file
+ DBML - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate DBML
     
    1. Produce your manifest json
     
    In your dbt project (I am using dbt-resto/integration_tests for demo purpose), try to build the docs:
     
     dbt docs generate 01:40:58 Running with dbt=1.3.4 01:40:58 Partial parse save file not found. Starting full parse. 01:41:00 Found 0 models, 0 tests, 0 snapshots, 0 analyses, 356 macros, 1 operation, 0 seed files, 0 sources, 0 exposures, 0 metrics 01:41:00  01:41:00 Concurrency: 4 threads (target='postgres') 01:41:00  01:41:00 Done. 01:41:00 Building catalog 01:41:00 Catalog written to .\target\catalog.json 
     
    2. Generate DBML
     
    Copy manifest.json and catalog.json into a specific folder OR do nothing and let's assume we're using dbt/target directory, and run
     
     
    Sample Usage
     
    dbterd run -ad "/path/to/dbt/target" -o "/path/to/output"
     
     
     dbterd run -ad "samples/dbtresto" -s model.dbt_resto 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.dbml (base.py:75) 
     
    File ./target/output.dbml will be generated as the result
     
    3. Build database docs site (Optional)
     
    Assuming you're already familiar with dbdocs
     
     
    Sample Usage
     
    dbdocs build "/path/to/output/output.dbml"
     
     
     dbdocs build "./target/output.dbml" √ Parsing file content ? Project name: poc ‼ Password is not set for 'poc' √ Done. Visit: https://dbdocs.io/datnguye/poc 
     
    The site will be looks like:
     
    screencapture-dbdocs-io-datnguye-poc-2022-12-18-22_02_28.png
     
    Result after applied Model Selection: screencapture-dbdocs-io-datnguye-poc-2023-02-25-10_29_32.png
      
     
      
      
      
     
     
     
             
\ No newline at end of file
diff --git a/1.8/nav/guide/targets/generate-graphviz.html b/1.8/nav/guide/targets/generate-graphviz.html
index f94dcdd..3620e84 100644
--- a/1.8/nav/guide/targets/generate-graphviz.html
+++ b/1.8/nav/guide/targets/generate-graphviz.html
@@ -1,4 +1,4 @@
- GraphViz - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate GraphViz ERD
     
    1. Install GraphViz CLI
     
    sudo apt install graphviz
+ GraphViz - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate GraphViz ERD
     
    1. Install GraphViz CLI
     
    sudo apt install graphviz
 
     
     
    Check installations for more details
     
     
    2. Generate GraphViz ERD content
     
     dbterd run -t graphviz -ad "samples/dbtresto" -s schema:dbt.mart 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.graphviz (base.py:75) 
     
    2. Export to PNG
     
     dot -Tpng ./target/output.d2 > ./target/output.png  
     
    3. Embeded into Markdown
     
    # Sample GraphViz ERD
 
 ![graphviz](./target/output.png)
diff --git a/1.8/nav/guide/targets/generate-markdown-mermaid-erd.html b/1.8/nav/guide/targets/generate-markdown-mermaid-erd.html
index f537586..e1a1617 100644
--- a/1.8/nav/guide/targets/generate-markdown-mermaid-erd.html
+++ b/1.8/nav/guide/targets/generate-markdown-mermaid-erd.html
@@ -1 +1 @@
- Mermaid - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate Markdown with Mermaid ERD inclusive
     
    1. Generate mermaid ERD content
     
     dbterd run -t mermaid -ad "samples/dbtresto" -s schema:dbt.mart 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.md (base.py:75) 
     
    2. Copy mermaid to ERD.md
     
     
    Linux/MacOs
     
    We'll use echo and cat to copy content over into the target Markdown file.
     
     
     echo \`\`\`mermaid > ./samples/dbtresto/ERD.md echo --- >> ./samples/dbtresto/ERD.md echo title: Sample ERD >> ./samples/dbtresto/ERD.md echo --- >> ./samples/dbtresto/ERD.md cat ./target/output.md >> ./samples/dbtresto/ERD.md echo \`\`\` >> ./samples/dbtresto/ERD.md  
     
    3. Commit it and check it on Github
     
    Check out the sample output:
     
    erd
      
     
      
      
      
     
     
     
             
\ No newline at end of file
+ Mermaid - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate Markdown with Mermaid ERD inclusive
     
    1. Generate mermaid ERD content
     
     dbterd run -t mermaid -ad "samples/dbtresto" -s schema:dbt.mart 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.md (base.py:75) 
     
    2. Copy mermaid to ERD.md
     
     
    Linux/MacOs
     
    We'll use echo and cat to copy content over into the target Markdown file.
     
     
     echo \`\`\`mermaid > ./samples/dbtresto/ERD.md echo --- >> ./samples/dbtresto/ERD.md echo title: Sample ERD >> ./samples/dbtresto/ERD.md echo --- >> ./samples/dbtresto/ERD.md cat ./target/output.md >> ./samples/dbtresto/ERD.md echo \`\`\` >> ./samples/dbtresto/ERD.md  
     
    3. Commit it and check it on Github
     
    Check out the sample output:
     
    erd
      
     
      
      
      
     
     
     
             
\ No newline at end of file
diff --git a/1.8/nav/guide/targets/generate-plantuml.html b/1.8/nav/guide/targets/generate-plantuml.html
index c583edb..27c7588 100644
--- a/1.8/nav/guide/targets/generate-plantuml.html
+++ b/1.8/nav/guide/targets/generate-plantuml.html
@@ -1,2 +1,2 @@
- PlantUML - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate PlantUML
     
    1. Generate PlantUML ERD content
     
     dbterd run -t plantuml -ad "samples/dbtresto" -s schema:dbt.mart 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.plantuml (base.py:75) 
     
    2. Wrapping UML up to the web server
     
       
    • Go to PlantUML Web Server
      •  
    • Paste the PlantUML content generated as above
      •  
    • Wait for a second and get the URL
      •  
     
    3. Embeded the PlantUML URL into Markdown
     
    ![](https://www.plantuml.com/plantuml/dpng/{your-hash})
+ PlantUML - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Generate PlantUML
     
    1. Generate PlantUML ERD content
     
     dbterd run -t plantuml -ad "samples/dbtresto" -s schema:dbt.mart 2023-05-06 08:17:54,413 - dbterd - INFO - Run with dbterd==?.?.? (main.py:54) 2023-05-06 08:17:54,715 - dbterd - INFO - target/output.plantuml (base.py:75) 
     
    2. Wrapping UML up to the web server
     
       
    • Go to PlantUML Web Server
      •  
    • Paste the PlantUML content generated as above
      •  
    • Wait for a second and get the URL
      •  
     
    3. Embeded the PlantUML URL into Markdown
     
    ![](https://www.plantuml.com/plantuml/dpng/{your-hash})
 
     
    erd
     
    Known Limitation💡
     
       
    • Plant UML connectors seem not to support to indicate the columns which are related to the Relationship
      •  
    • Left the question "How to automate the markdown image URL generated?" opened
      •  
      
     
      
      
      
     
     
     
             
\ No newline at end of file
diff --git a/1.8/nav/metadata/ignore_in_erd.html b/1.8/nav/metadata/ignore_in_erd.html
index 2d20cb1..fd5517f 100644
--- a/1.8/nav/metadata/ignore_in_erd.html
+++ b/1.8/nav/metadata/ignore_in_erd.html
@@ -1,4 +1,4 @@
- Ignore Tests - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Ignore Tests
     
    Decide to exclude Relationship Tests from ERD generated
     
    Add ignore_in_erd attribute into your test's meta: 
    version: 2
+ Ignore Tests - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Ignore Tests
     
    Decide to exclude Relationship Tests from ERD generated
     
    Add ignore_in_erd attribute into your test's meta: 
    version: 2
 
 models:
   - name: your_model
diff --git a/1.8/nav/metadata/relationship_type.html b/1.8/nav/metadata/relationship_type.html
index 7fd4260..01ae482 100644
--- a/1.8/nav/metadata/relationship_type.html
+++ b/1.8/nav/metadata/relationship_type.html
@@ -1,4 +1,4 @@
- Relationship Types - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Relationship Types
     
    Decide to enforce Relationship Type
     
    Add relationship_type attribute into your test's meta:
     
    version: 2
+ Relationship Types - DaaC from dbt artifacts      
     
      
      
     
     
     
     
     
     
      
     
     
     
     
     
      
     
     
     
     
           
    Relationship Types
     
    Decide to enforce Relationship Type
     
    Add relationship_type attribute into your test's meta:
     
    version: 2
 
 models:
   - name: your_model
diff --git a/1.8/sitemap.xml b/1.8/sitemap.xml
index bbebf0f..79e8088 100644
--- a/1.8/sitemap.xml
+++ b/1.8/sitemap.xml
@@ -2,67 +2,67 @@
 
     
          https://datnguye.github.io/dbterd/1.8/index.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/license.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/development/CHANGELOG.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/development/contributing-guide.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/cli-references.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/dbt-cloud/download-artifact-from-a-job-run.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/targets/generate-d2.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/targets/generate-dbml.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/targets/generate-graphviz.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/targets/generate-markdown-mermaid-erd.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/guide/targets/generate-plantuml.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/metadata/ignore_in_erd.html
-         2024-01-06
+         2024-01-12
          daily
     
     
          https://datnguye.github.io/dbterd/1.8/nav/metadata/relationship_type.html
-         2024-01-06
+         2024-01-12
          daily
     
 
\ No newline at end of file
diff --git a/1.8/sitemap.xml.gz b/1.8/sitemap.xml.gz
index 38259c5..c4381a7 100644
Binary files a/1.8/sitemap.xml.gz and b/1.8/sitemap.xml.gz differ