diff --git a/docs/guides/dbt_docs/generating-docs.rst b/docs/guides/dbt_docs/generating-docs.rst index 2d7820a5d3..f6bef71558 100644 --- a/docs/guides/dbt_docs/generating-docs.rst +++ b/docs/guides/dbt_docs/generating-docs.rst @@ -121,7 +121,7 @@ Choosing a folder All the DbtDocsOperators support specification of a custom folder (prefix) to place documentation in on the target cloud storage. This can be done by adding a ``folder_dir`` parameter to the operator definition. -Static Flag +Static flag ''''''''''' All of the DbtDocsOperator accept the ``--static`` flag. To learn more about the static flag, check out the `original PR on dbt-core `_. @@ -149,7 +149,7 @@ The following code snippet shows how to provide this flag with the default jaffl dbt_cmd_flags=["--static"], ) -Custom Callback +Custom callback ''''''''''''''' If you want to run custom code after the docs are generated, you can use the :class:`~cosmos.operators.DbtDocsOperator`. The following code snippet shows how to do this with the default jaffle_shop project: diff --git a/docs/guides/index.rst b/docs/guides/index.rst index 5ea1515c23..20b512bc39 100644 --- a/docs/guides/index.rst +++ b/docs/guides/index.rst @@ -77,7 +77,7 @@ Specify more details about how Cosmos runs both dbt commands and Airflow Dags. T run_dbt/operators/index run_dbt/customization/index -Multi-project Setups +Multi-project setups ++++++++++++++++++++ If you have a multi-project architecture where you have multiple dbt projects that reference each others' models, you can set up ``dbt-loom`` with Cosmos to handle cross-project references. diff --git a/docs/guides/multi_project/multi-project.rst b/docs/guides/multi_project/multi-project.rst index d0381c6110..49640da435 100644 --- a/docs/guides/multi_project/multi-project.rst +++ b/docs/guides/multi_project/multi-project.rst @@ -1,6 +1,6 @@ .. _multi-project: -Multi-Project Setups +Multi-project setups -------------------- Cosmos supports multi-project dbt architectures where multiple dbt projects reference each other's models. @@ -15,7 +15,7 @@ This allows you to: Cosmos works with dbt-loom out of the box, automatically handling external node references. -How dbt-loom Works +How dbt-loom works ++++++++++++++++++ dbt-loom enables cross-project references by: @@ -24,7 +24,7 @@ dbt-loom enables cross-project references by: 2. Injecting the upstream models' metadata into the downstream project's namespace 3. Allowing cross-project references using the dbt Mesh syntax: ``{{ ref('upstream_project', 'model_name') }}`` -How Cosmos Handles dbt-loom +How Cosmos handles dbt-loom +++++++++++++++++++++++++++ When Cosmos parses a dbt project that uses dbt-loom, it encounters two types of nodes: @@ -62,10 +62,10 @@ The upstream manifest can be generated by running any dbt command that parses th # or dbt ls # Lists resources and generates manifest -Configuration Example +Configuration example +++++++++++++++++++++ -Project Structure +Project structure ''''''''''''''''' A typical dbt-loom setup has an upstream project and one or more downstream projects: @@ -92,7 +92,7 @@ A typical dbt-loom setup has an upstream project and one or more downstream proj └── models/ └── fct_revenue.sql # References upstream models -Upstream Project Configuration +Upstream project configuration '''''''''''''''''''''''''''''' The upstream project exposes models as ``public`` for cross-project access: @@ -115,7 +115,7 @@ The upstream project exposes models as ``public`` for cross-project access: +materialized: view +access: public -Downstream Project Configuration +Downstream project configuration '''''''''''''''''''''''''''''''' The downstream project configures dbt-loom to read from the upstream manifest. @@ -335,7 +335,7 @@ To disable automatic asset emission: # ... ) -Cross-Project Sources +Cross-project sources +++++++++++++++++++++ dbt-loom handles **model references** but does not directly support cross-project source references @@ -397,7 +397,7 @@ If you must reference the same raw table in multiple projects, define the source This approach requires keeping source definitions in sync across projects. -Cross-Project Macros +Cross-project macros ++++++++++++++++++++ dbt-loom does **not** handle macro sharing. Macros are resolved at compile time within each project. diff --git a/docs/guides/run_dbt/airflow-worker/async-execution-mode.rst b/docs/guides/run_dbt/airflow-worker/async-execution-mode.rst index 78f415d939..a608254f24 100644 --- a/docs/guides/run_dbt/airflow-worker/async-execution-mode.rst +++ b/docs/guides/run_dbt/airflow-worker/async-execution-mode.rst @@ -36,7 +36,7 @@ We have `observed `_ +----------------------------------------------+--------------------------+ -Getting Started with Airflow Async Mode +Getting started with Airflow async mode +++++++++++++++++++++++++++++++++++++++ This guide walks you through setting up an Astro CLI project and running a Cosmos-based DAG with a deferrable operator, enabling asynchronous task execution in Apache Airflow. @@ -47,7 +47,7 @@ Prerequisites - `Astro CLI `_ - Airflow>=2.9 -1. Create Astro-CLI Project +1. Create Astro-CLI project ''''''''''''''''''''''''''' Run the following command in your terminal: @@ -82,7 +82,7 @@ Edit your Dockerfile to ensure all necessary requirements are included. FROM astrocrpublic.azurecr.io/runtime:3.0-2 -3. Add astronomer-cosmos Dependency +3. Add astronomer-cosmos dependency ''''''''''''''''''''''''''''''''''' In your ``requirements.txt``, add: diff --git a/docs/guides/run_dbt/airflow-worker/watcher-execution-mode.rst b/docs/guides/run_dbt/airflow-worker/watcher-execution-mode.rst index 8a590d68ec..15d231af31 100644 --- a/docs/guides/run_dbt/airflow-worker/watcher-execution-mode.rst +++ b/docs/guides/run_dbt/airflow-worker/watcher-execution-mode.rst @@ -1,6 +1,6 @@ .. _watcher-execution-mode: -Watcher execution mode (Experimental) +Watcher execution mode (experimental) ------------------------------------- With the release of **Cosmos 1.11.0**, we are introducing a powerful new experimental execution mode — ``ExecutionMode.WATCHER`` — designed to drastically reduce dbt pipeline run times in `Apache Airflow® `_. @@ -12,7 +12,7 @@ Early benchmarks show that ``ExecutionMode.WATCHER`` can cut total DAG runtime * - The ``poke_interval`` and ``timeout`` settings of the ``DbtConsumerWatcherSensor`` operator, which determine the frequency and duration of the sensor's polling. -Background: The Problem with the Local Execution Mode in Cosmos +Background: The problem with the local execution mode in Cosmos +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ When running dbt via Cosmos using the default ``ExecutionMode.LOCAL``, each dbt model is executed as a separate Airflow task. @@ -52,7 +52,7 @@ Together, these operators let you: - Retry specific models (for resilience) -Performance Gains +Performance gains +++++++++++++++++ We used a dbt project developed by Google, the `google/fhir-dbt-analytics `_ project, that interfaces with BigQuery. It contains: @@ -128,7 +128,7 @@ If you prefer to manage threads through Cosmos profile mappings instead of editi -Example Usage of ``ExecutionMode.WATCHER`` +Example usage of ``ExecutionMode.WATCHER`` ++++++++++++++++++++++++++++++++++++++++++ There are two main ways to use the new execution mode in Cosmos — directly within a ``DbtDag``, or embedded as part of a ``DbtTaskGroup`` inside a larger DAG. @@ -341,7 +341,7 @@ Starting with Cosmos 1.12.0, the ``DbtConsumerWatcherSensor`` supports which increases overall task throughput. By default, the sensor now runs in deferrable mode. -Known Limitations +Known limitations +++++++++++++++++ Producer task implementation diff --git a/docs/guides/run_dbt/container/kubernetes.rst b/docs/guides/run_dbt/container/kubernetes.rst index 47eee363b6..e619779a39 100644 --- a/docs/guides/run_dbt/container/kubernetes.rst +++ b/docs/guides/run_dbt/container/kubernetes.rst @@ -171,7 +171,7 @@ Enable and trigger a run of the `jaffle_shop_k8s `_ to power scheduling, you can leverage Airflow's scheduling capabilities to schedule your dbt projects. This includes cron-based scheduling, timetables, and data-aware scheduling. For more info on Airflow's scheduling capabilities, check out the Airflow documentation or check out the `Astronomer documentation `_. -Time-Based Scheduling +Time-based scheduling +++++++++++++++++++++ To schedule a dbt project on a time-based schedule, you can use Airflow's scheduling options. For example, to run a dbt project every day starting on January 1, 2023, you can use the following DAG: @@ -22,7 +22,7 @@ To schedule a dbt project on a time-based schedule, you can use Airflow's schedu .. _data-aware-scheduling: -Data-Aware Scheduling +Data-aware scheduling +++++++++++++++++++++ `Apache Airflow® `_ 2.4 introduced the concept of `scheduling based on Datasets `_. @@ -247,7 +247,7 @@ How Dataset Emission Differs by Execution Mode emitted URIs by enabling the ``enable_uri_xcom`` setting (see `Emitting Dataset URIs as XCom`_). -Known Limitations +Known limitations ''''''''''''''''' Airflow 3.0 and beyond diff --git a/docs/guides/translate_dbt_to_airflow/managing-sources.rst b/docs/guides/translate_dbt_to_airflow/managing-sources.rst index c72756d917..42f56c57d5 100644 --- a/docs/guides/translate_dbt_to_airflow/managing-sources.rst +++ b/docs/guides/translate_dbt_to_airflow/managing-sources.rst @@ -1,6 +1,6 @@ .. _managing-sources: -Managing Sources +Managing sources ---------------- .. note:: @@ -37,7 +37,7 @@ Example: ) -Source Pruning +Source pruning ++++++++++++++ The ``source_pruning`` is a boolean parameter available in the ``RenderConfig``. @@ -63,7 +63,7 @@ Example: In this example, if the ``jaffle_shop`` project has multiple sources, but only some of them are upstream of the ``customers`` model, Cosmos will only render the necessary sources and prune the rest. -on_warning_callback Callback +on_warning_callback callback ++++++++++++++++++++++++++++ The ``on_warning_callback`` is a callback parameter available on the ``DbtSourceLocalOperator``. This callback is triggered when a warning occurs during the execution of the ``dbt source freshness`` command. The callback accepts the task context, which includes additional parameters: test_names and test_results diff --git a/docs/guides/translate_dbt_to_airflow/testing-behavior.rst b/docs/guides/translate_dbt_to_airflow/testing-behavior.rst index 83b574f4c0..0678a64f3f 100644 --- a/docs/guides/translate_dbt_to_airflow/testing-behavior.rst +++ b/docs/guides/translate_dbt_to_airflow/testing-behavior.rst @@ -1,9 +1,9 @@ .. _testing-behavior: -Testing Behavior +Testing behavior ---------------- -Testing Configuration +Testing configuration +++++++++++++++++++++ By default, Cosmos will add a test after each model. This can be overridden using the ``test_behavior`` field in the ``RenderConfig`` object. @@ -49,7 +49,7 @@ Finally, an example DAG and how it is rendered in the `Apache Airflow® `_ or in the `cosmos-demo repo `_. -Join the Community +Join the community ------------------ Have questions, need help, or interested in contributing? We welcome all contributions and feedback! diff --git a/docs/optimize_performance/invocation_mode.rst b/docs/optimize_performance/invocation_mode.rst index 00df076f08..68a928ed67 100644 --- a/docs/optimize_performance/invocation_mode.rst +++ b/docs/optimize_performance/invocation_mode.rst @@ -1,6 +1,6 @@ .. _invocation-mode: -Invocation Modes +Invocation modes ---------------- .. versionadded:: 1.4 diff --git a/docs/optimize_performance/memory_optimization.rst b/docs/optimize_performance/memory_optimization.rst index 7d1eba01e4..467a733569 100644 --- a/docs/optimize_performance/memory_optimization.rst +++ b/docs/optimize_performance/memory_optimization.rst @@ -1,13 +1,13 @@ .. _memory-optimization: -Memory Optimization Options for Astronomer Cosmos -------------------------------------------------- +Memory optimization options for Astronomer Cosmos +-------------------------------------------------- When running dbt pipelines with Astronomer Cosmos, the framework executes dbt commands that can consume significant memory resources. In high-memory scenarios, tasks may reach a zombie state or workers may be killed due to Out of Memory (OOM) errors, leading to pipeline failures and reduced reliability. Cosmos provides various configuration options and execution modes to optimize memory usage, reduce worker resource consumption, and prevent OOM issues. This document outlines these memory optimization strategies, from simple configuration changes to advanced execution modes that can dramatically reduce memory footprint while maintaining or improving pipeline performance. -1. Use DBT_MANIFEST Load Mode +1. Use DBT_MANIFEST load mode +++++++++++++++++++++++++++++ **Impact**: High - Avoids running ``dbt ls`` subprocess which can consume significant CPU and memory. This reduces memory consumption when a cache miss occurs in the DBT LS method. It may not significantly reduce the memory footprint if there is a cache hit. @@ -33,7 +33,7 @@ Cosmos provides various configuration options and execution modes to optimize me **Requirements**: You need a ``manifest.json`` file (can be generated with ``dbt compile`` or ``dbt run``). -2. Use DBT_RUNNER Invocation Mode +2. Use DBT_RUNNER invocation mode +++++++++++++++++++++++++++++++++ - (default for ``ExecutionMode.LOCAL`` since 1.4.0, default for ``RenderConfig.DBT_LS`` since Cosmos 1.9.0) @@ -64,7 +64,7 @@ Cosmos provides various configuration options and execution modes to optimize me **Default**: default behaviour for ``ExecutionMode.LOCAL`` since 1.4.0, default behaviour for ``RenderConfig.DBT_LS`` since Cosmos 1.9.0 -3. Use Partial Parse (Keep Enabled) +3. Use partial parse (keep enabled) +++++++++++++++++++++++++++++++++++ **Impact**: Low - Actually reduces memory by avoiding full project parsing. @@ -101,7 +101,7 @@ Cosmos provides various configuration options and execution modes to optimize me - `Configure a Custom Queue for Producer and Watcher Tasks in ExecutionMode.WATCHER `_ -5. Control DAG-Level Concurrency with ``concurrency`` Parameter +5. Control DAG-level concurrency with ``concurrency`` parameter +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ **Impact**: High - Limits concurrent task execution per DAG based on available resources. @@ -169,7 +169,7 @@ Cosmos provides various configuration options and execution modes to optimize me **Reference**: `Airflow Scaling Workers Documentation `_ -6. Enable Memory-Optimized Imports (Cosmos < 1.14.0 only) +6. Enable memory-optimized imports (Cosmos < 1.14.0 only) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ **Applies to**: Cosmos versions **earlier than 1.14.0**. Since Cosmos 1.14.0, ``cosmos/__init__.py`` uses lazy imports by default and this setting is a no-op. If you are on 1.14.0 or newer, skip this section. @@ -205,7 +205,7 @@ Cosmos provides various configuration options and execution modes to optimize me **Default**: ``False`` -7. Enable Task Profiling with Debug Mode +7. Enable task profiling with debug mode ++++++++++++++++++++++++++++++++++++++++ **Impact**: Low - Provides visibility into memory usage patterns to help identify optimization opportunities and prevent OOM issues. diff --git a/docs/policy/airflow3-compatibility.rst b/docs/policy/airflow3-compatibility.rst index 13bb8136cb..d7dfdca59b 100644 --- a/docs/policy/airflow3-compatibility.rst +++ b/docs/policy/airflow3-compatibility.rst @@ -1,6 +1,6 @@ .. _airflow3-compatibility: -Apache Airflow® 3 Compatibility (First Iteration) +Apache Airflow® 3 compatibility (first iteration) -------------------------------------------------- The Cosmos 1.10.0 release marks the **first iteration** of adding compatibility for `Apache Airflow® 3 `_ @@ -32,7 +32,7 @@ If you want to use the Airflow 3 URI standard while still using Airflow 2, pleas Remember to update any DAGs that are triggered using Cosmos-generated datasets or aliases to the new URI format. -What Works +What works ++++++++++ With the changes contributed in Cosmos 1.10.0 to bring in compatibility with Airflow 3, we have validated Cosmos’ @@ -87,7 +87,7 @@ You can set the same mapping via the Airflow config environment variable ``AIRFL Docs are available at ``/cosmos//dbt_docs_index.html``. Static assets are served directly for local directories or proxied for remote storage (S3/GCS/Azure/HTTP). -Validation in Progress +Validation in progress ++++++++++++++++++++++ We are actively validating the combined support for `Assets `_ @@ -96,13 +96,13 @@ This may be **unstable** in Cosmos 1.10.0. Bug reports are very welcome. We encourage users to try it out and provide feedback, but note that certain edge cases may still be under investigation. -Known Limitations +Known limitations +++++++++++++++++ Airflow 3 DatasetAlias no longer support ASCII characters. This issue has been reported to the `Airflow community `_ and we are also tracking it in the `Cosmos repository `_. -What's Next +What's next +++++++++++ We are actively tracking open issues and enhancements related to **Airflow 3 compatibility** in Cosmos. diff --git a/docs/policy/compatibility-policy.rst b/docs/policy/compatibility-policy.rst index bc2b569b71..7c4ca8a4f0 100644 --- a/docs/policy/compatibility-policy.rst +++ b/docs/policy/compatibility-policy.rst @@ -1,6 +1,6 @@ .. _compatibility-policy: -Compatibility Policy +Compatibility policy -------------------- This document outlines Astronomer Cosmos's compatibility policy for Python, @@ -23,7 +23,7 @@ This policy establishes: - User guidance for planning upgrades and checking compatibility - Contributor guidance for proposing version changes -Currently Supported Versions +Currently supported versions ++++++++++++++++++++++++++++ The following versions are currently tested and supported. @@ -55,14 +55,14 @@ dbt Core Refer to the `dbt documentation `_ for adapter-specific version compatibility. -Version Removal Policy +Version removal policy ++++++++++++++++++++++ Cosmos removes support for versions based on clear and objective criteria. There is no deprecation period—versions are removed when they meet the removal criteria. -Python Version Removal Criteria +Python version removal criteria ''''''''''''''''''''''''''''''' Python versions are removed from support when **any** of the following @@ -75,7 +75,7 @@ conditions are met: - **Astronomer Runtime incompatibility**: Astronomer Runtime no longer supports the Python version -Apache Airflow Version Removal Criteria +Apache Airflow version removal criteria ''''''''''''''''''''''''''''''''''''''' Apache Airflow versions are removed from support when **both** of the @@ -88,7 +88,7 @@ following conditions are met: Basic Support according to the `Astronomer Runtime lifecycle policy `_ -dbt Core Version Removal Criteria +dbt Core version removal criteria ''''''''''''''''''''''''''''''''' dbt Core versions are removed from support when: @@ -96,7 +96,7 @@ dbt Core versions are removed from support when: - **dbt Core EOL**: The dbt Core version has reached End of Life according to the `dbt Labs support policy `_ -Version Removal Process +Version removal process +++++++++++++++++++++++ When a version meets the removal criteria: @@ -109,10 +109,10 @@ When a version meets the removal criteria: 4. **Removal**: Support is removed from the test matrix and CI/CD pipeline in the next release -User Guidance +User guidance +++++++++++++ -Checking Compatibility +Checking compatibility '''''''''''''''''''''' Before upgrading Cosmos or its dependencies: @@ -124,7 +124,7 @@ Before upgrading Cosmos or its dependencies: 4. **Monitor GitHub issues and releases**: Check for known compatibility issues or migration guides -Planning Upgrades +Planning upgrades ''''''''''''''''' To minimize disruption: @@ -137,7 +137,7 @@ To minimize disruption: EOL - **Use CI/CD**: Test compatibility in your CI/CD pipeline before deploying -Reporting Compatibility Issues +Reporting compatibility issues '''''''''''''''''''''''''''''' If you encounter compatibility issues: @@ -150,10 +150,10 @@ If you encounter compatibility issues: 3. **Include versions**: Specify Python, Airflow, dbt Core, and Cosmos versions in your report -Contributor Guidance +Contributor guidance ++++++++++++++++++++ -Proposing Version Changes +Proposing version changes ''''''''''''''''''''''''' When proposing to add or remove version support: @@ -172,7 +172,7 @@ When proposing to add or remove version support: 4. **Verify criteria**: Ensure removal proposals meet the criteria outlined in this policy -Updating Test Matrix +Updating test matrix '''''''''''''''''''' When adding or removing versions: @@ -184,7 +184,7 @@ When adding or removing versions: 3. **Update documentation**: Update this compatibility policy document 4. **Update CHANGELOG.rst**: Document the change in the changelog -Testing Requirements +Testing requirements '''''''''''''''''''' All supported version combinations should: @@ -205,7 +205,7 @@ How do I know when a version will be removed? - **Subscribe to releases**: Get notified of new releases that may include version removals -Related Documentation +Related documentation ''''''''''''''''''''' - `CHANGELOG.rst `_ diff --git a/docs/policy/contributing.rst b/docs/policy/contributing.rst index cd50f66177..77082843f8 100644 --- a/docs/policy/contributing.rst +++ b/docs/policy/contributing.rst @@ -207,7 +207,7 @@ To run the checks manually, run: pre-commit run --all-files -Writing Docs +Writing docs ++++++++++++ `Hatch `_ is a unified command-line tool for managing dependencies and environment isolation for Python developers. In Cosmos, we use a Hatch to declare the dependencies required for the project itself, as well as for tests and documentation builds. diff --git a/docs/policy/contributors.rst b/docs/policy/contributors.rst index 32925c22e2..a63e3d4f4e 100644 --- a/docs/policy/contributors.rst +++ b/docs/policy/contributors.rst @@ -18,7 +18,7 @@ Committers - Tatiana Al-Chueyr (`@tatiana `_) -Emeritus Committers +Emeritus committers +++++++++++++++++++ - Chris Hronek (`@chrishronek `_) diff --git a/docs/policy/policies.rst b/docs/policy/policies.rst index 352846fa68..d4cc135109 100644 --- a/docs/policy/policies.rst +++ b/docs/policy/policies.rst @@ -1,8 +1,8 @@ Cosmos project policies ----------------------- -Project Repositories and Subprojects -+++++++++++++++++++++++++++++++++++++ +Project repositories and subprojects +++++++++++++++++++++++++++++++++++++ The following repositories constitute the codebases for the Astronomer Cosmos project for compliance purposes (OSPS-QA-04.01): @@ -16,14 +16,14 @@ The following repositories constitute the codebases for the Astronomer Cosmos pr Note: There are no additional subproject codebases beyond the repositories listed above for OSPS-QA-04.01 compliance purposes. -Versioning Policy +Versioning policy +++++++++++++++++ We follow `Semantic Versioning `_ for releases. Refer to `CHANGELOG.rst `_ for the latest changes. -Privacy Notice +Privacy notice ++++++++++++++ The application and this website collect telemetry to support the project's development. These can be disabled by the end-users. diff --git a/docs/policy/security.rst b/docs/policy/security.rst index 295f5925f8..dcf434e30d 100644 --- a/docs/policy/security.rst +++ b/docs/policy/security.rst @@ -1,14 +1,14 @@ Cosmos security --------------- -Security Policy +Security policy +++++++++++++++ Check the project's `Security Policy `_ to learn how to report security vulnerabilities in Astronomer Cosmos and how security issues reported to the Astronomer Cosmos security team are handled. -Dependency Update Cooldown +Dependency update cooldown ++++++++++++++++++++++++++ To mitigate the risk of supply chain attacks from newly released versions, Cosmos enforces a **7-day cooldown period** diff --git a/docs/reference/configs/project-config.rst b/docs/reference/configs/project-config.rst index 7c5bd20071..bb8c6de350 100644 --- a/docs/reference/configs/project-config.rst +++ b/docs/reference/configs/project-config.rst @@ -1,6 +1,6 @@ .. _project-config: -Project Config +Project config -------------- The ``cosmos.config.ProjectConfig`` allows you to specify information about where your dbt project is located and project @@ -28,7 +28,7 @@ variables that should be used for rendering and execution. It takes the followin for the ``LoadMode.DBT_LS`` load mode, and for the ``ExecutionMode.LOCAL`` and ``ExecutionMode.VIRTUALENV`` execution modes. Due to the way that dbt `partial parsing works `_, it does not work with Cosmos profile mapping classes. To benefit from this feature, users have to set the ``profiles_yml_filepath`` argument in ``ProfileConfig``. -Project Config Example +Project config example ++++++++++++++++++++++ .. code-block:: python diff --git a/docs/reference/templates/profile_mapping.rst.jinja2 b/docs/reference/templates/profile_mapping.rst.jinja2 index 0fd031e983..481435d577 100644 --- a/docs/reference/templates/profile_mapping.rst.jinja2 +++ b/docs/reference/templates/profile_mapping.rst.jinja2 @@ -56,7 +56,7 @@ Some notes about the table above: ``extra.token``. {% if profile_defaults %} -Default Values +Default values -------------- This profile mapping sets the following default values. These can be overridden by passing