[DOCS]: Port over "How to instantiate a Data Context w/o YML" from RTD to Docusaurus #3011
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ Deploy Preview for knoxpod ready! 🔨 Explore the source changes: 79fdad8 🔍 Inspect the deploy log: https://app.netlify.com/sites/knoxpod/deploys/60e8c3b7976d160008b6901a 😎 Browse the preview: https://deploy-preview-3011--knoxpod.netlify.app |
HOWDY! This is your friendly 🤖 CHANGELOG bot 🤖Please don't forget to add a clear and succinct description of your change under the Develop header in ✨ Thank you! ✨ |
…_context_wo_yml' of github.com:great-expectations/great_expectations into DOCS/GDOC-107/GDOC-58/port_over_how_to_instantiate_data_context_wo_yml
cdkini
changed the title
cdkini
commented
Jul 9, 2021
|
|
||
| Here we will show a few examples of common configurations, using the ``store_backend_defaults`` parameter. Note that you can continue with the existing API sans defaults by omitting this parameter, and you can override all of the parameters as shown in the last example. Note that a parameter set in ``DataContextConfig`` will override a parameter set in ``store_backend_defaults`` if both are used. | ||
|
|
||
| **TODO(cdkini): These are links to our API Reference, which has not yet been implemented. What should we do here?** |
There was a problem hiding this comment.
Please note this TODO here and below.
cdkini
commented
Jul 9, 2021
|
|
||
| If you are using Airflow, you may wish to pass this Data Context to your GreatExpectationsOperator as a parameter. See the following guide for more details: | ||
|
|
||
| - [Deploying Great Expectations with Airflow](../../../guides/w) - **TODO(cdkini): Where do we link this?** |
There was a problem hiding this comment.
Please note this TODO here; we do not have this file in our new docs.
…stantiate_data_context_wo_yml
…stantiate_data_context_wo_yml
cdkini
deleted the
DOCS/GDOC-107/GDOC-58/port_over_how_to_instantiate_data_context_wo_yml
branch
pasmavie
pushed a commit
to pasmavie/great_expectations
that referenced
this pull request
Jul 13, 2021
…TD to Docusaurus (great-expectations#3011) * docs: Port over guide from RTD to Docusaurus
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please annotate your PR title to describe what the PR does, then give a brief bulleted description of your PR below. PR titles should begin with [BUGFIX], [FEATURE], [DOCS], or [MAINTENANCE]. If a new feature introduces breaking changes for the Great Expectations API or configuration files, please also add [BREAKING]. You can read about the tags in our contributor checklist.
Changes proposed in this pull request:
.rstguide to.mdAfter submitting your PR, CI checks will run and @tiny-tim-bot will check for your CLA signature.
For a PR with nontrivial changes, we review with both design-centric and code-centric lenses.
In a design review, we aim to ensure that the PR is consistent with our relationship to the open source community, with our software architecture and abstractions, and with our users' needs and expectations. That review often starts well before a PR, for example in github issues or slack, so please link to relevant conversations in notes below to help reviewers understand and approve your PR more quickly (e.g.
closes #123).Previous Design Review notes:
Definition of Done
Please delete options that are not relevant.
Thank you for submitting!