[DOCS] Removes remaining OSS docs from the prerelease version (#9582)

great-expectations · Mar 11, 2024 · 3f65ae3 · 3f65ae3
1 parent c476eb2
commit 3f65ae3
Show file tree

Hide file tree

Showing 372 changed files with 191 additions and 24,511 deletions.
diff --git a/docs/docusaurus/docs/application_integration_support.md b/docs/docusaurus/docs/application_integration_support.md
@@ -67,10 +67,10 @@ The following table defines the supported GX Cloud and GX OSS integrations.
 
 The following table defines the GX components supported by GX Cloud and GX OSS.
 
-| Component                                | GX Cloud             | GX OSS                                                                    |
-|------------------------------------------|----------------------|---------------------------------------------------------------------------|
-| Expectations                             | See [Available Expectations](/cloud/expectations/manage_expectations.md#available-expectations). | See [Create Expectations](/oss/guides/expectations/expectations_lp.md). |
-| GX Agent                                 | All versions               | N/A                                                                       |
+| Component                                | GX Cloud             | GX OSS                                                                       |
+|------------------------------------------|----------------------|------------------------------------------------------------------------------|
+| Expectations                             | See [Available Expectations](/cloud/expectations/manage_expectations.md#available-expectations). | See [Create Expectations](/core/create_expectations/create_expectations.md). |
+| GX Agent                                 | All versions               | N/A                                                                          |
 
 
 ## Community-supported

diff --git a/docs/docusaurus/docs/cloud/checkpoints/manage_checkpoints.md b/docs/docusaurus/docs/cloud/checkpoints/manage_checkpoints.md
@@ -6,7 +6,7 @@ description: Create and manage Checkpoints in GX Cloud.
 
 A Checkpoint validates Expectation Suite data. After you create a Checkpoint to validate data, you can save and reuse the Checkpoint. 
 
-To learn more about Checkpoints, see [Checkpoint](/reference/learn/terms/checkpoint.md).
+<!-- [//]: # (TODO: To learn more about Checkpoints, see Checkpoint.) -->
 
 ## Prerequisites
 
@@ -84,7 +84,7 @@ To learn more about Checkpoints, see [Checkpoint](/reference/learn/terms/checkpo
 
 ## Add a Validation to a Checkpoint
 
-Add Validation data to a Checkpoint to aggregate individual Expectation Suite or Data Source Validations into a single Checkpoint. For more information, see [Add Validation data or Expectation Suites to a Checkpoint](../../oss/guides/validation/checkpoints/how_to_add_validations_data_or_suites_to_a_checkpoint.md) in the GX OSS documentaion.
+Add Validation data to a Checkpoint to aggregate individual Expectation Suite or Data Source Validations into a single Checkpoint. For more information, see [Manage Checkpoints](/core/validate_data/manage_checkpoints.md) in the GX 1.0 documentaion.
 
 1. In GX Cloud, click **Checkpoints**.
 
@@ -149,7 +149,9 @@ Add Validation data to a Checkpoint to aggregate individual Expectation Suite or
 
 ## Configure the Checkpoint result format parameter 
 
-You can use the `result_format` parameter to define the level of detail you want returned with your Validation Results. For example, you can return a success or failure message, a summary of observed values, a list of failing values, or you can add a query or a filter function that returns all failing rows. For more information, see [Result format](../../reference/learn/expectations/result_format.md).
+You can use the `result_format` parameter to define the level of detail you want returned with your Validation Results. For example, you can return a success or failure message, a summary of observed values, a list of failing values, or you can add a query or a filter function that returns all failing rows. 
+
+<!-- [//]: # (TODO: For more information, see Result format.) -->
 
 Run the following code to apply `result_format` to every Expectation in a Suite:
 

diff --git a/docs/docusaurus/docs/cloud/connect/connect_python.md b/docs/docusaurus/docs/cloud/connect/connect_python.md
@@ -4,10 +4,6 @@ title: 'Connect to GX Cloud with Python'
 id: connect_python
 description: Connect to a GX Cloud account and validate data from a Python script.
 ---
-import Prerequisites from '../../components/_prerequisites.jsx'
-import PrereqPython from '../../components/prerequisites/_python_version.md'
-import SetupAndInstallGx from '../../components/setup/link_lists/_setup_and_install_gx.md'
-import DataContextInitializeInstantiateSave from '../../components/setup/link_lists/_data_context_initialize_instatiate_save.md'
 
 In this quickstart, you'll learn how to use GX Cloud from a Python script or interpreter, such as a Jupyter Notebook. You'll install Great Expectations, configure your GX Cloud environment variables, connect to sample data, build your first Expectation, validate data, and review the validation results through Python code.
 
@@ -115,12 +111,3 @@ Environment variables securely store your GX Cloud access credentials.
 
     ```python title="Python" name="tutorials/quickstart/quickstart.py view_results"
     ```
-
-## Related documentation
-
-
-- [Install GX in a specific environment with a specific Data Source](/oss/guides/setup/installation/install_gx.md)
-- [Initialize, instantiate, and save a Data Context](/oss/guides/setup/configure_data_contexts_lp.md)
-- [Connect to Data Sources](/oss/guides/connecting_to_your_data/connect_to_data_lp.md)
-- [Create and manage Expectations and Expectation Suites](/oss/guides/expectations/expectations_lp.md)
-- [Create, manage, and run Checkpoints](/oss/guides/validation/checkpoints/checkpoint_lp.md)
diff --git a/docs/docusaurus/docs/cloud/data_assets/manage_data_assets.md b/docs/docusaurus/docs/cloud/data_assets/manage_data_assets.md
@@ -11,12 +11,12 @@ import Tabs from '@theme/Tabs';
 
 A Data Asset is a collection of records that you create when you connect to your Data Source. When you connect to your Data Source, you define a minimum of one Data Asset. You use these Data Assets to create the Batch Requests that select the data that is provided to your Expectations.
 
-To learn more about Data Assets, see [Data Asset](/reference/learn/terms/data_asset.md).
+<!-- [//]: # (TODO: To learn more about Data Assets, see Data Asset.) -->
 
 
 ## Create a Data Asset
 
-Create a Data Asset to define the data you want GX Cloud to access. To connect to Data Assets for a Data Source not currently available in GX Cloud, see [Connect to a Data Source](/oss/guides/connecting_to_your_data/connect_to_data_lp.md) in the GX OSS documentation. 
+Create a Data Asset to define the data you want GX Cloud to access. To connect to Data Assets for a Data Source not currently available in GX Cloud, see [Connect to a data](/core/manage_and_access_data/connect_to_data/connect_to_data.md) in the GX 1.0 documentation. 
 
 <Tabs
   groupId="manage-data-assets"

diff --git a/docs/docusaurus/docs/cloud/expectation_suites/manage_expectation_suites.md b/docs/docusaurus/docs/cloud/expectation_suites/manage_expectation_suites.md
@@ -6,7 +6,7 @@ description: Create and manage Expectation Suites in GX Cloud.
 
 Expectation Suites contain multiple Expectations for a single Data Asset. Like Expectations, they can help you better understand your data and help you improve data quality. A default Expectation Suite is created when you create a Data Asset. 
 
-To learn more about Expectation Suites, see [Expectation Suites](/reference/learn/terms/expectation_suite.md).
+<!-- [//]: # (TODO: To learn more about Expectation Suites, see Expectation Suites.) -->
 
 ## Prerequisites
 

diff --git a/docs/docusaurus/docs/cloud/expectations/manage_expectations.md b/docs/docusaurus/docs/cloud/expectations/manage_expectations.md
@@ -6,7 +6,7 @@ description: Create and manage Expectations in GX Cloud.
 
 An Expectation is a verifiable assertion about your data. They make implicit assumptions about your data explicit, and they provide a flexible, declarative language for describing expected behavior. They can help you better understand your data and help you improve data quality. An Expectation Suite contains multiple Expectations.
 
-To learn more about Expectations, see [Expectation](/reference/learn/terms/expectation.md).
+<!-- [//]: # (TODO: To learn more about Expectations, see Expectation.) -->
 
 ## Prerequisites
 

diff --git a/docs/docusaurus/docs/cloud/try_gx_cloud.md b/docs/docusaurus/docs/cloud/try_gx_cloud.md
@@ -144,7 +144,7 @@ Create a Data Asset to define the data you want GX Cloud to access within Snowfl
 
 10. Optional. Select **Add Data Asset** to add additional tables or queries and repeat steps 8 and 9.
 
-11. Click **Finish**. The Data Asset(s), a default empty [Expectation Suite](../reference/learn/terms/expectation_suite.md), and a default [Checkpoint](../reference/learn/terms/checkpoint.md) are created.
+11. Click **Finish**. The Data Asset(s), a default empty Expectation Suite, and a default Checkpoint are created.
 
 </TabItem>
 <TabItem value="PostgreSQL">
@@ -187,7 +187,7 @@ Define the data you want GX Cloud to access within PostgreSQL.
 
 9. Optional. Select **Add Data Asset** to add additional tables or queries and repeat steps 8 and 9.
 
-10. Click **Finish**. The Data Asset(s), a default empty [Expectation Suite](../reference/learn/terms/expectation_suite.md), and a default [Checkpoint](../reference/learn/terms/checkpoint.md) are created. 
+10. Click **Finish**. The Data Asset(s), a default empty Expectation Suite, and a default Checkpoint are created. 
 
 </TabItem>
 </Tabs>

diff --git a/docs/docusaurus/docs/cloud/validations/manage_validations.md b/docs/docusaurus/docs/cloud/validations/manage_validations.md
@@ -6,7 +6,7 @@ description: Create and manage Validations in GX Cloud.
 
 When you run a validation on an Expectation, a Checkpoint is added. The Checkpoint saves the Validation Results, runs the Actions you specify, and displays the Validation Results.
 
-To learn more about Validations, see [Validator](/reference/learn/terms/validator.md).
+<!-- [//]: # (TODO: To learn more about Validations, see Validator.) -->
 
 ## Prerequisites
 

diff --git a/docs/docusaurus/docs/components/_prerequisites.jsx b/docs/docusaurus/docs/components/_prerequisites.jsx
diff --git a/...s/components/connect_to_data/link_lists/_connect_to_filesystem_data_fluently.md b/...s/components/connect_to_data/link_lists/_connect_to_filesystem_data_fluently.md
diff --git a/...cs/components/connect_to_data/link_lists/_connect_to_in_memory_data_fluently.md b/...cs/components/connect_to_data/link_lists/_connect_to_in_memory_data_fluently.md
diff --git a/...urus/docs/components/connect_to_data/link_lists/_connecting_to_data_fluently.md b/...urus/docs/components/connect_to_data/link_lists/_connecting_to_data_fluently.md
diff --git a/...omponents/connect_to_data/link_lists/_connecting_to_sql_datasources_fluently.md b/...omponents/connect_to_data/link_lists/_connecting_to_sql_datasources_fluently.md
diff --git a/...rus/docs/components/connect_to_data/link_lists/_work_with_fluent_data_assets.md b/...rus/docs/components/connect_to_data/link_lists/_work_with_fluent_data_assets.md
diff --git a/...components/connect_to_data/next_steps/_after_create_and_configure_data_asset.md b/...components/connect_to_data/next_steps/_after_create_and_configure_data_asset.md
diff --git a/...ocs/components/connect_to_data/next_steps/_after_create_in_memory_data_asset.md b/...ocs/components/connect_to_data/next_steps/_after_create_in_memory_data_asset.md
diff --git a/.../docs/components/connect_to_data/next_steps/_after_create_non_sql_datasource.md b/.../docs/components/connect_to_data/next_steps/_after_create_non_sql_datasource.md
diff --git a/...urus/docs/components/connect_to_data/next_steps/_after_create_sql_data_asset.md b/...urus/docs/components/connect_to_data/next_steps/_after_create_sql_data_asset.md
diff --git a/...urus/docs/components/connect_to_data/next_steps/_after_create_sql_datasource.md b/...urus/docs/components/connect_to_data/next_steps/_after_create_sql_datasource.md
diff --git a/...ocusaurus/docs/components/connect_to_data/next_steps/_after_create_validator.md b/...ocusaurus/docs/components/connect_to_data/next_steps/_after_create_validator.md
diff --git a/.../components/connect_to_data/next_steps/_after_request_data_from_a_data_asset.md b/.../components/connect_to_data/next_steps/_after_request_data_from_a_data_asset.md
diff --git a/...aurus/docs/components/prerequisites/_abs_configured_an_azure_storage_account.md b/...aurus/docs/components/prerequisites/_abs_configured_an_azure_storage_account.md
diff --git a/...quisites/_abs_configured_an_azure_storage_account_and_kept_connection_string.md b/...quisites/_abs_configured_an_azure_storage_account_and_kept_connection_string.md
diff --git a/...ocusaurus/docs/components/prerequisites/_abs_created_an_azure_blob_container.md b/...ocusaurus/docs/components/prerequisites/_abs_created_an_azure_blob_container.md
diff --git a/...requisites/_abs_permissions_to_create_and_configure_an_azure_storage_account.md b/...requisites/_abs_permissions_to_create_and_configure_an_azure_storage_account.md
diff --git a/docs/docusaurus/docs/components/prerequisites/_aws_configured_your_credentials.mdx b/docs/docusaurus/docs/components/prerequisites/_aws_configured_your_credentials.mdx
diff --git a/docs/docusaurus/docs/components/prerequisites/_aws_installed_the_aws_cli.mdx b/docs/docusaurus/docs/components/prerequisites/_aws_installed_the_aws_cli.mdx
diff --git a/docs/docusaurus/docs/components/prerequisites/_gcp_service_account.md b/docs/docusaurus/docs/components/prerequisites/_gcp_service_account.md
diff --git a/docs/docusaurus/docs/components/prerequisites/_if_you_still_need_to_setup_gx.md b/docs/docusaurus/docs/components/prerequisites/_if_you_still_need_to_setup_gx.md