We are currently solving the following issue within our repository. Here is the issue text:
--- BEGIN ISSUE ---
great_expectations.yml has broken links
Working off the latest version:

```
→ great_expectations --version

great_expectations, version 0.8.4.post0
```


YAML file generated from `great_expectations init` has the following contents:

```yaml

# Welcome to Great Expectations! Always know what to expect from your data.
# 
# Here you can define datasources, generators, integrations and more. This file
# is intended to be committed to your repo. For help with configuration please:
#   - Read our docs: https://docs.greatexpectations.io/en/0_8_4_post0/reference/data_context_reference.html#configuration
#   - Join our slack channel: http://greatexpectations.io/slack
#
# NOTE: GE uses the names of configured `datasources` and `generators` to manage
# how `expectations` and other artifacts are stored in the `expectations/` and 
# `datasources/` folders. If you need to rename an existing `datasource` or 
# `generator`, be sure to also update the relevant directory names.

config_version: 1

# Datasources tell Great Expectations where your data lives and how to get it.
# You can use the CLI command `great_expectations add-datasource` to help you
# add a new datasource. Read more at https://docs.greatexpectations.io/en/0_8_4_post0/features/datasource.html
datasources:
  test:
    class_name: PandasDatasource
    data_asset_type:
      class_name: PandasDataset
    generators:
      default:
        class_name: SubdirReaderGenerator
        base_directory: ../misc
        reader_options:
          sep:
          engine: python
```


All the docs linked throughout the yaml file, i.e. https://docs.greatexpectations.io/en/0_8_4_post0/features/datasource.html, do not exist.

Missing link/reference in docs?
https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#validation-operators

![image](https://user-images.githubusercontent.com/11096727/68488005-24e6e500-0212-11ea-8e95-013d74a52096.png)

Assuming the underlined part should have a hyperlink?

--- END ISSUE ---

Below are some code segments, each from a relevant file. One or more of these files may contain bugs.
--- BEGIN FILES ---
Path: `great_expectations/data_context/templates.py`
Content:
```
1 # -*- coding: utf-8 -*-
2 from great_expectations import rtd_url_ge_version
3 
4 PROJECT_HELP_COMMENT = """
5 # Welcome to Great Expectations! Always know what to expect from your data.
6 # 
7 # Here you can define datasources, generators, integrations and more. This file
8 # is intended to be committed to your repo. For help with configuration please:
9 #   - Read our docs: https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/data_context_reference.html#configuration
10 #   - Join our slack channel: http://greatexpectations.io/slack
11 #
12 # NOTE: GE uses the names of configured `datasources` and `generators` to manage
13 # how `expectations` and other artifacts are stored in the `expectations/` and 
14 # `datasources/` folders. If you need to rename an existing `datasource` or 
15 # `generator`, be sure to also update the relevant directory names.
16 
17 config_version: 1
18 
19 # Datasources tell Great Expectations where your data lives and how to get it.
20 # You can use the CLI command `great_expectations add-datasource` to help you
21 # add a new datasource. Read more at https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/features/datasource.html
22 datasources: {}
23 """
24 
25 CONFIG_VARIABLES_INTRO = """
26 # This config file supports variable substitution which enables: 1) keeping
27 # secrets out of source control & 2) environment-based configuration changes
28 # such as staging vs prod.
29 #
30 # When GE encounters substitution syntax (like `my_key: ${my_value}` or 
31 # `my_key: $my_value`) in the config file it will attempt to replace the value
32 # of `my_key` with the value from an environment variable `my_value` or a
33 # corresponding key read from the file specified using
34 # `config_variables_file_path`. Environment variables take precedence.
35 #
36 # If the substitution value comes from the config variables file, it can be a
37 # simple (non-nested) value or a nested value such as a dictionary. If it comes
38 # from an environment variable, it must be a simple value. Read more at:
39 # https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/data_context_reference.html#managing-environment-and-secrets"""
40 
41 # This junky fake key keeps ruaml.yml from nuking the important comment block
42 CONFIG_VARIABLES_TEMPLATE = "ge_comment_preservation_key: 1" + CONFIG_VARIABLES_INTRO
43 
44 PROJECT_OPTIONAL_CONFIG_COMMENT = CONFIG_VARIABLES_INTRO + """
45 config_variables_file_path: uncommitted/config_variables.yml
46 
47 # The plugins_directory will be added to your python path for custom modules
48 # used to override and extend Great Expectations.
49 plugins_directory: plugins/
50 
51 # Validation Operators are customizable workflows that bundle the validation of
52 # one or more expectation suites and subsequent actions. The example below
53 # stores validations and send a slack notification. To read more about
54 # customizing and extending these, read: https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/features/validation_operators_and_actions.html
55 validation_operators:
56   action_list_operator:
57     # To learn how to configure sending Slack notifications during evaluation
58     # (and other customizations), read: https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/validation_operators/action_list_validation_operator.html
59     class_name: ActionListValidationOperator
60     action_list:
61       - name: store_validation_result
62         action:
63           class_name: StoreAction
64       - name: store_evaluation_params
65         action:
66           class_name: ExtractAndStoreEvaluationParamsAction
67       - name: update_data_docs
68         action:
69           class_name: UpdateDataDocsAction
70       - name: send_slack_notification_on_validation_result
71         action:
72           class_name: SlackNotificationAction
73           # put the actual webhook URL in the uncommitted/config_variables.yml file
74           slack_webhook: ${validation_notification_slack_webhook}
75           notify_on: all # possible values: "all", "failure", "success"
76           renderer:
77             module_name: great_expectations.render.renderer.slack_renderer
78             class_name: SlackRenderer
79     
80 stores:
81 # Stores are configurable places to store things like Expectations, Validations
82 # Data Docs, and more. These are for advanced users only - most users can simply
83 # leave this section alone.
84 # 
85 # Three stores are required: expectations, validations, and
86 # evaluation_parameters, and must exist with a valid store entry. Additional
87 # stores can be configured for uses such as data_docs, validation_operators, etc.
88   expectations_store:
89     class_name: ExpectationsStore
90     store_backend:
91       class_name: FixedLengthTupleFilesystemStoreBackend
92       base_directory: expectations/
93 
94   validations_store:
95     class_name: ValidationsStore
96     store_backend:
97       class_name: FixedLengthTupleFilesystemStoreBackend
98       base_directory: uncommitted/validations/
99 
100   evaluation_parameter_store:
101     # Evaluation Parameters enable dynamic expectations. Read more here:
102     # https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/evaluation_parameters.html
103     class_name: InMemoryEvaluationParameterStore
104 
105 expectations_store_name: expectations_store
106 validations_store_name: validations_store
107 evaluation_parameter_store_name: evaluation_parameter_store
108 
109 data_docs_sites:
110   # Data Docs make it simple to visualize data quality in your project. These
111   # include Expectations, Validations & Profiles. The are built for all
112   # Datasources from JSON artifacts in the local repo including validations &
113   # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/features/data_docs.html
114   local_site:
115     class_name: SiteBuilder
116     store_backend:
117         class_name: FixedLengthTupleFilesystemStoreBackend
118         base_directory: uncommitted/data_docs/local_site/
119     site_index_builder:
120         show_cta_footer: True
121 """
122 
123 PROJECT_TEMPLATE = PROJECT_HELP_COMMENT + PROJECT_OPTIONAL_CONFIG_COMMENT
124
```
--- END FILES ---

Please first localize the bug based on the issue statement, and then generate a patch according to the `git diff` format fenced by three backticks.

Here is an example:

```diff
diff --git a/examples/server_async.py b/examples/server_async.py
--- a/examples/server_async.py
+++ b/examples/server_async.py
@@ -313,4 +313,4 @@
 
 
 if __name__ == "__main__":
-    asyncio.run(run_async_server("."), debug=True)
+    asyncio.run(run_async_server(), debug=True)
diff --git a/examples/server_sync.py b/examples/server_sync.py
--- a/examples/server_sync.py
+++ b/examples/server_sync.py
@@ -313,5 +313,5 @@
 
 
 if __name__ == "__main__":
-    server = run_sync_server(".")
+    server = run_sync_server()
     server.shutdown()

```

diff --git a/great_expectations/data_context/templates.py b/great_expectations/data_context/templates.py
--- a/great_expectations/data_context/templates.py
+++ b/great_expectations/data_context/templates.py
@@ -6,7 +6,7 @@
 # 
 # Here you can define datasources, generators, integrations and more. This file
 # is intended to be committed to your repo. For help with configuration please:
-#   - Read our docs: https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/data_context_reference.html#configuration
+#   - Read our docs: https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#configuration
 #   - Join our slack channel: http://greatexpectations.io/slack
 #
 # NOTE: GE uses the names of configured `datasources` and `generators` to manage
@@ -18,7 +18,7 @@
 
 # Datasources tell Great Expectations where your data lives and how to get it.
 # You can use the CLI command `great_expectations add-datasource` to help you
-# add a new datasource. Read more at https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/features/datasource.html
+# add a new datasource. Read more at https://docs.greatexpectations.io/en/latest/features/datasource.html
 datasources: {}
 """
 
@@ -36,7 +36,7 @@
 # If the substitution value comes from the config variables file, it can be a
 # simple (non-nested) value or a nested value such as a dictionary. If it comes
 # from an environment variable, it must be a simple value. Read more at:
-# https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/data_context_reference.html#managing-environment-and-secrets"""
+# https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#managing-environment-and-secrets"""
 
 # This junky fake key keeps ruaml.yml from nuking the important comment block
 CONFIG_VARIABLES_TEMPLATE = "ge_comment_preservation_key: 1" + CONFIG_VARIABLES_INTRO
@@ -51,11 +51,11 @@
 # Validation Operators are customizable workflows that bundle the validation of
 # one or more expectation suites and subsequent actions. The example below
 # stores validations and send a slack notification. To read more about
-# customizing and extending these, read: https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/features/validation_operators_and_actions.html
+# customizing and extending these, read: https://docs.greatexpectations.io/en/latest/features/validation_operators_and_actions.html
 validation_operators:
   action_list_operator:
     # To learn how to configure sending Slack notifications during evaluation
-    # (and other customizations), read: https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/validation_operators/action_list_validation_operator.html
+    # (and other customizations), read: https://docs.greatexpectations.io/en/latest/reference/validation_operators/action_list_validation_operator.html
     class_name: ActionListValidationOperator
     action_list:
       - name: store_validation_result
@@ -99,7 +99,7 @@
 
   evaluation_parameter_store:
     # Evaluation Parameters enable dynamic expectations. Read more here:
-    # https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/reference/evaluation_parameters.html
+    # https://docs.greatexpectations.io/en/latest/reference/evaluation_parameters.html
     class_name: InMemoryEvaluationParameterStore
 
 expectations_store_name: expectations_store
@@ -110,7 +110,7 @@
   # Data Docs make it simple to visualize data quality in your project. These
   # include Expectations, Validations & Profiles. The are built for all
   # Datasources from JSON artifacts in the local repo including validations &
-  # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/""" + rtd_url_ge_version + """/features/data_docs.html
+  # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/latest/features/data_docs.html
   local_site:
     class_name: SiteBuilder
     store_backend:

{"golden_diff": "diff --git a/great_expectations/data_context/templates.py b/great_expectations/data_context/templates.py\n--- a/great_expectations/data_context/templates.py\n+++ b/great_expectations/data_context/templates.py\n@@ -6,7 +6,7 @@\n # \n # Here you can define datasources, generators, integrations and more. This file\n # is intended to be committed to your repo. For help with configuration please:\n-#   - Read our docs: https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/data_context_reference.html#configuration\n+#   - Read our docs: https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#configuration\n #   - Join our slack channel: http://greatexpectations.io/slack\n #\n # NOTE: GE uses the names of configured `datasources` and `generators` to manage\n@@ -18,7 +18,7 @@\n \n # Datasources tell Great Expectations where your data lives and how to get it.\n # You can use the CLI command `great_expectations add-datasource` to help you\n-# add a new datasource. Read more at https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/features/datasource.html\n+# add a new datasource. Read more at https://docs.greatexpectations.io/en/latest/features/datasource.html\n datasources: {}\n \"\"\"\n \n@@ -36,7 +36,7 @@\n # If the substitution value comes from the config variables file, it can be a\n # simple (non-nested) value or a nested value such as a dictionary. If it comes\n # from an environment variable, it must be a simple value. Read more at:\n-# https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/data_context_reference.html#managing-environment-and-secrets\"\"\"\n+# https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#managing-environment-and-secrets\"\"\"\n \n # This junky fake key keeps ruaml.yml from nuking the important comment block\n CONFIG_VARIABLES_TEMPLATE = \"ge_comment_preservation_key: 1\" + CONFIG_VARIABLES_INTRO\n@@ -51,11 +51,11 @@\n # Validation Operators are customizable workflows that bundle the validation of\n # one or more expectation suites and subsequent actions. The example below\n # stores validations and send a slack notification. To read more about\n-# customizing and extending these, read: https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/features/validation_operators_and_actions.html\n+# customizing and extending these, read: https://docs.greatexpectations.io/en/latest/features/validation_operators_and_actions.html\n validation_operators:\n   action_list_operator:\n     # To learn how to configure sending Slack notifications during evaluation\n-    # (and other customizations), read: https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/validation_operators/action_list_validation_operator.html\n+    # (and other customizations), read: https://docs.greatexpectations.io/en/latest/reference/validation_operators/action_list_validation_operator.html\n     class_name: ActionListValidationOperator\n     action_list:\n       - name: store_validation_result\n@@ -99,7 +99,7 @@\n \n   evaluation_parameter_store:\n     # Evaluation Parameters enable dynamic expectations. Read more here:\n-    # https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/evaluation_parameters.html\n+    # https://docs.greatexpectations.io/en/latest/reference/evaluation_parameters.html\n     class_name: InMemoryEvaluationParameterStore\n \n expectations_store_name: expectations_store\n@@ -110,7 +110,7 @@\n   # Data Docs make it simple to visualize data quality in your project. These\n   # include Expectations, Validations & Profiles. The are built for all\n   # Datasources from JSON artifacts in the local repo including validations &\n-  # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/features/data_docs.html\n+  # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/latest/features/data_docs.html\n   local_site:\n     class_name: SiteBuilder\n     store_backend:\n", "issue": "great_expectations.yml has broken links\nWorking off the latest version:\r\n\r\n```\r\n\u2192 great_expectations --version\r\n\r\ngreat_expectations, version 0.8.4.post0\r\n```\r\n\r\n\r\nYAML file generated from `great_expectations init` has the following contents:\r\n\r\n```yaml\r\n\r\n# Welcome to Great Expectations! Always know what to expect from your data.\r\n# \r\n# Here you can define datasources, generators, integrations and more. This file\r\n# is intended to be committed to your repo. For help with configuration please:\r\n#   - Read our docs: https://docs.greatexpectations.io/en/0_8_4_post0/reference/data_context_reference.html#configuration\r\n#   - Join our slack channel: http://greatexpectations.io/slack\r\n#\r\n# NOTE: GE uses the names of configured `datasources` and `generators` to manage\r\n# how `expectations` and other artifacts are stored in the `expectations/` and \r\n# `datasources/` folders. If you need to rename an existing `datasource` or \r\n# `generator`, be sure to also update the relevant directory names.\r\n\r\nconfig_version: 1\r\n\r\n# Datasources tell Great Expectations where your data lives and how to get it.\r\n# You can use the CLI command `great_expectations add-datasource` to help you\r\n# add a new datasource. Read more at https://docs.greatexpectations.io/en/0_8_4_post0/features/datasource.html\r\ndatasources:\r\n  test:\r\n    class_name: PandasDatasource\r\n    data_asset_type:\r\n      class_name: PandasDataset\r\n    generators:\r\n      default:\r\n        class_name: SubdirReaderGenerator\r\n        base_directory: ../misc\r\n        reader_options:\r\n          sep:\r\n          engine: python\r\n```\r\n\r\n\r\nAll the docs linked throughout the yaml file, i.e. https://docs.greatexpectations.io/en/0_8_4_post0/features/datasource.html, do not exist.\r\n\nMissing link/reference in docs?\nhttps://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#validation-operators\r\n\r\n![image](https://user-images.githubusercontent.com/11096727/68488005-24e6e500-0212-11ea-8e95-013d74a52096.png)\r\n\r\nAssuming the underlined part should have a hyperlink?\n", "before_files": [{"content": "# -*- coding: utf-8 -*-\nfrom great_expectations import rtd_url_ge_version\n\nPROJECT_HELP_COMMENT = \"\"\"\n# Welcome to Great Expectations! Always know what to expect from your data.\n# \n# Here you can define datasources, generators, integrations and more. This file\n# is intended to be committed to your repo. For help with configuration please:\n#   - Read our docs: https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/data_context_reference.html#configuration\n#   - Join our slack channel: http://greatexpectations.io/slack\n#\n# NOTE: GE uses the names of configured `datasources` and `generators` to manage\n# how `expectations` and other artifacts are stored in the `expectations/` and \n# `datasources/` folders. If you need to rename an existing `datasource` or \n# `generator`, be sure to also update the relevant directory names.\n\nconfig_version: 1\n\n# Datasources tell Great Expectations where your data lives and how to get it.\n# You can use the CLI command `great_expectations add-datasource` to help you\n# add a new datasource. Read more at https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/features/datasource.html\ndatasources: {}\n\"\"\"\n\nCONFIG_VARIABLES_INTRO = \"\"\"\n# This config file supports variable substitution which enables: 1) keeping\n# secrets out of source control & 2) environment-based configuration changes\n# such as staging vs prod.\n#\n# When GE encounters substitution syntax (like `my_key: ${my_value}` or \n# `my_key: $my_value`) in the config file it will attempt to replace the value\n# of `my_key` with the value from an environment variable `my_value` or a\n# corresponding key read from the file specified using\n# `config_variables_file_path`. Environment variables take precedence.\n#\n# If the substitution value comes from the config variables file, it can be a\n# simple (non-nested) value or a nested value such as a dictionary. If it comes\n# from an environment variable, it must be a simple value. Read more at:\n# https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/data_context_reference.html#managing-environment-and-secrets\"\"\"\n\n# This junky fake key keeps ruaml.yml from nuking the important comment block\nCONFIG_VARIABLES_TEMPLATE = \"ge_comment_preservation_key: 1\" + CONFIG_VARIABLES_INTRO\n\nPROJECT_OPTIONAL_CONFIG_COMMENT = CONFIG_VARIABLES_INTRO + \"\"\"\nconfig_variables_file_path: uncommitted/config_variables.yml\n\n# The plugins_directory will be added to your python path for custom modules\n# used to override and extend Great Expectations.\nplugins_directory: plugins/\n\n# Validation Operators are customizable workflows that bundle the validation of\n# one or more expectation suites and subsequent actions. The example below\n# stores validations and send a slack notification. To read more about\n# customizing and extending these, read: https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/features/validation_operators_and_actions.html\nvalidation_operators:\n  action_list_operator:\n    # To learn how to configure sending Slack notifications during evaluation\n    # (and other customizations), read: https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/validation_operators/action_list_validation_operator.html\n    class_name: ActionListValidationOperator\n    action_list:\n      - name: store_validation_result\n        action:\n          class_name: StoreAction\n      - name: store_evaluation_params\n        action:\n          class_name: ExtractAndStoreEvaluationParamsAction\n      - name: update_data_docs\n        action:\n          class_name: UpdateDataDocsAction\n      - name: send_slack_notification_on_validation_result\n        action:\n          class_name: SlackNotificationAction\n          # put the actual webhook URL in the uncommitted/config_variables.yml file\n          slack_webhook: ${validation_notification_slack_webhook}\n          notify_on: all # possible values: \"all\", \"failure\", \"success\"\n          renderer:\n            module_name: great_expectations.render.renderer.slack_renderer\n            class_name: SlackRenderer\n    \nstores:\n# Stores are configurable places to store things like Expectations, Validations\n# Data Docs, and more. These are for advanced users only - most users can simply\n# leave this section alone.\n# \n# Three stores are required: expectations, validations, and\n# evaluation_parameters, and must exist with a valid store entry. Additional\n# stores can be configured for uses such as data_docs, validation_operators, etc.\n  expectations_store:\n    class_name: ExpectationsStore\n    store_backend:\n      class_name: FixedLengthTupleFilesystemStoreBackend\n      base_directory: expectations/\n\n  validations_store:\n    class_name: ValidationsStore\n    store_backend:\n      class_name: FixedLengthTupleFilesystemStoreBackend\n      base_directory: uncommitted/validations/\n\n  evaluation_parameter_store:\n    # Evaluation Parameters enable dynamic expectations. Read more here:\n    # https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/reference/evaluation_parameters.html\n    class_name: InMemoryEvaluationParameterStore\n\nexpectations_store_name: expectations_store\nvalidations_store_name: validations_store\nevaluation_parameter_store_name: evaluation_parameter_store\n\ndata_docs_sites:\n  # Data Docs make it simple to visualize data quality in your project. These\n  # include Expectations, Validations & Profiles. The are built for all\n  # Datasources from JSON artifacts in the local repo including validations &\n  # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/\"\"\" + rtd_url_ge_version + \"\"\"/features/data_docs.html\n  local_site:\n    class_name: SiteBuilder\n    store_backend:\n        class_name: FixedLengthTupleFilesystemStoreBackend\n        base_directory: uncommitted/data_docs/local_site/\n    site_index_builder:\n        show_cta_footer: True\n\"\"\"\n\nPROJECT_TEMPLATE = PROJECT_HELP_COMMENT + PROJECT_OPTIONAL_CONFIG_COMMENT\n", "path": "great_expectations/data_context/templates.py"}], "after_files": [{"content": "# -*- coding: utf-8 -*-\nfrom great_expectations import rtd_url_ge_version\n\nPROJECT_HELP_COMMENT = \"\"\"\n# Welcome to Great Expectations! Always know what to expect from your data.\n# \n# Here you can define datasources, generators, integrations and more. This file\n# is intended to be committed to your repo. For help with configuration please:\n#   - Read our docs: https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#configuration\n#   - Join our slack channel: http://greatexpectations.io/slack\n#\n# NOTE: GE uses the names of configured `datasources` and `generators` to manage\n# how `expectations` and other artifacts are stored in the `expectations/` and \n# `datasources/` folders. If you need to rename an existing `datasource` or \n# `generator`, be sure to also update the relevant directory names.\n\nconfig_version: 1\n\n# Datasources tell Great Expectations where your data lives and how to get it.\n# You can use the CLI command `great_expectations add-datasource` to help you\n# add a new datasource. Read more at https://docs.greatexpectations.io/en/latest/features/datasource.html\ndatasources: {}\n\"\"\"\n\nCONFIG_VARIABLES_INTRO = \"\"\"\n# This config file supports variable substitution which enables: 1) keeping\n# secrets out of source control & 2) environment-based configuration changes\n# such as staging vs prod.\n#\n# When GE encounters substitution syntax (like `my_key: ${my_value}` or \n# `my_key: $my_value`) in the config file it will attempt to replace the value\n# of `my_key` with the value from an environment variable `my_value` or a\n# corresponding key read from the file specified using\n# `config_variables_file_path`. Environment variables take precedence.\n#\n# If the substitution value comes from the config variables file, it can be a\n# simple (non-nested) value or a nested value such as a dictionary. If it comes\n# from an environment variable, it must be a simple value. Read more at:\n# https://docs.greatexpectations.io/en/latest/reference/data_context_reference.html#managing-environment-and-secrets\"\"\"\n\n# This junky fake key keeps ruaml.yml from nuking the important comment block\nCONFIG_VARIABLES_TEMPLATE = \"ge_comment_preservation_key: 1\" + CONFIG_VARIABLES_INTRO\n\nPROJECT_OPTIONAL_CONFIG_COMMENT = CONFIG_VARIABLES_INTRO + \"\"\"\nconfig_variables_file_path: uncommitted/config_variables.yml\n\n# The plugins_directory will be added to your python path for custom modules\n# used to override and extend Great Expectations.\nplugins_directory: plugins/\n\n# Validation Operators are customizable workflows that bundle the validation of\n# one or more expectation suites and subsequent actions. The example below\n# stores validations and send a slack notification. To read more about\n# customizing and extending these, read: https://docs.greatexpectations.io/en/latest/features/validation_operators_and_actions.html\nvalidation_operators:\n  action_list_operator:\n    # To learn how to configure sending Slack notifications during evaluation\n    # (and other customizations), read: https://docs.greatexpectations.io/en/latest/reference/validation_operators/action_list_validation_operator.html\n    class_name: ActionListValidationOperator\n    action_list:\n      - name: store_validation_result\n        action:\n          class_name: StoreAction\n      - name: store_evaluation_params\n        action:\n          class_name: ExtractAndStoreEvaluationParamsAction\n      - name: update_data_docs\n        action:\n          class_name: UpdateDataDocsAction\n      - name: send_slack_notification_on_validation_result\n        action:\n          class_name: SlackNotificationAction\n          # put the actual webhook URL in the uncommitted/config_variables.yml file\n          slack_webhook: ${validation_notification_slack_webhook}\n          notify_on: all # possible values: \"all\", \"failure\", \"success\"\n          renderer:\n            module_name: great_expectations.render.renderer.slack_renderer\n            class_name: SlackRenderer\n    \nstores:\n# Stores are configurable places to store things like Expectations, Validations\n# Data Docs, and more. These are for advanced users only - most users can simply\n# leave this section alone.\n# \n# Three stores are required: expectations, validations, and\n# evaluation_parameters, and must exist with a valid store entry. Additional\n# stores can be configured for uses such as data_docs, validation_operators, etc.\n  expectations_store:\n    class_name: ExpectationsStore\n    store_backend:\n      class_name: FixedLengthTupleFilesystemStoreBackend\n      base_directory: expectations/\n\n  validations_store:\n    class_name: ValidationsStore\n    store_backend:\n      class_name: FixedLengthTupleFilesystemStoreBackend\n      base_directory: uncommitted/validations/\n\n  evaluation_parameter_store:\n    # Evaluation Parameters enable dynamic expectations. Read more here:\n    # https://docs.greatexpectations.io/en/latest/reference/evaluation_parameters.html\n    class_name: InMemoryEvaluationParameterStore\n\nexpectations_store_name: expectations_store\nvalidations_store_name: validations_store\nevaluation_parameter_store_name: evaluation_parameter_store\n\ndata_docs_sites:\n  # Data Docs make it simple to visualize data quality in your project. These\n  # include Expectations, Validations & Profiles. The are built for all\n  # Datasources from JSON artifacts in the local repo including validations &\n  # profiles from the uncommitted directory. Read more at https://docs.greatexpectations.io/en/latest/features/data_docs.html\n  local_site:\n    class_name: SiteBuilder\n    store_backend:\n        class_name: FixedLengthTupleFilesystemStoreBackend\n        base_directory: uncommitted/data_docs/local_site/\n    site_index_builder:\n        show_cta_footer: True\n\"\"\"\n\nPROJECT_TEMPLATE = PROJECT_HELP_COMMENT + PROJECT_OPTIONAL_CONFIG_COMMENT\n", "path": "great_expectations/data_context/templates.py"}]}