🎨 [pre-commit.ci] Auto format from pre-commit.com hooks

astronomer · Oct 11, 2023 · 23771cd · 23771cd
1 parent 774ea9f
commit 23771cd
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 7 deletions.
diff --git a/docs/getting_started/astro.rst b/docs/getting_started/astro.rst
@@ -110,7 +110,7 @@ In your ``my_cosmos_dag.py`` file, import the ``DbtDag`` class from Cosmos and c
     )
 
 .. note::
-   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. 
+   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``.
    The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest <https://astronomer.github.io/astronomer-cosmos/configuration/parsing-methods.html#dbt-manifest>`_.
    Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.
 

diff --git a/docs/getting_started/gcc.rst b/docs/getting_started/gcc.rst
@@ -80,6 +80,6 @@ Make sure to rename the ``<your-adapter>`` value below to your adapter's Python
 
 
 .. note::
-   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. 
+   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``.
    The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest <https://astronomer.github.io/astronomer-cosmos/configuration/parsing-methods.html#dbt-manifest>`_.
-   Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.
+   Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.
diff --git a/docs/getting_started/mwaa.rst b/docs/getting_started/mwaa.rst
@@ -114,6 +114,6 @@ In your ``my_cosmos_dag.py`` file, import the ``DbtDag`` class from Cosmos and c
 
 
 .. note::
-   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. 
+   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``.
    The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest <https://astronomer.github.io/astronomer-cosmos/configuration/parsing-methods.html#dbt-manifest>`_.
-   Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.
+   Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.
diff --git a/docs/getting_started/open-source.rst b/docs/getting_started/open-source.rst
@@ -66,6 +66,6 @@ For example, if you wanted to put your dbt project in the ``/usr/local/airflow/d
 
 
 .. note::
-   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. 
+   In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``.
    The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest <https://astronomer.github.io/astronomer-cosmos/configuration/parsing-methods.html#dbt-manifest>`_.
-   Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.
+   Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dagbag-import-timeout>`_.