Skip to content
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

Adding custom Salesforce connection type + SalesforceToS3Operator updates #17162

Merged
merged 9 commits into from
Jul 25, 2021

Conversation

josh-fell
Copy link
Contributor

@josh-fell josh-fell commented Jul 22, 2021

Closes: #8766

Creating a new Salesforce connection type. Currently, the security_token is exposed in plain text and setting up the connection is not intuitive.

  • Update SalesforceHook
  • Update Salesforce connection docs
  • Update SalesforceToS3Operator and SalesforceToGcsOperator
  • Update Salesforce Hook test

Here is the new connection form:

image

I also updated -- effectively reverted a change to -- the output of the SalesforceToS3Operator from a previous PR of mine because of the issue mentioned in this PR.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

@boring-cyborg boring-cyborg bot added area:providers kind:documentation provider:amazon-aws AWS/Amazon - related issues provider:google Google (including GCP) related issues labels Jul 22, 2021
@eladkal eladkal self-requested a review July 22, 2021 15:08
Copy link
Contributor

@eladkal eladkal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

(There are more connection parameters that can be configed it will be handled later #17192 )

@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Jul 25, 2021
@github-actions
Copy link

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers kind:documentation okay to merge It's ok to merge this PR as it does not require more tests provider:amazon-aws AWS/Amazon - related issues provider:google Google (including GCP) related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add custom Salesforce connection type
3 participants