New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add partner integration framework #5132
add partner integration framework #5132
Conversation
✅ Deploy Preview for niobium-lead-7998 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
* rubenshift works * add rubenshift job
* anthony db works! * add anthonydb job
…tions into MAINTENANCE/CLOUD-1070/add_partner_integrations_framework
👇 Click on the image for a new way to code review
Legend |
…rk' of github.com:great-expectations/great_expectations into MAINTENANCE/CLOUD-1070/add_partner_integrations_framework
…tions into MAINTENANCE/CLOUD-1070/add_partner_integrations_framework
…rk' of github.com:great-expectations/great_expectations into MAINTENANCE/CLOUD-1070/add_partner_integrations_framework
* add partner integration framework * set cron job * Demonstration: add partner integration type 2: Rubenshift (great-expectations#5130) * rubenshift works * add rubenshift job * Demonstration: add partner integration type 1: AnthonyDB (great-expectations#5133) * anthony db works! * add anthonydb job * fix cron format * envelope the until * merge into one Dockerfile * -y instead of force yes * -y instead of force yes * faster startup * move outside bash
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:
After submitting your PR, CI checks will run and @cla-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!