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

Add optional 'tenant' config option #111

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

robotfelix
Copy link

Description of change

Providing the "tenant ID" of a single tenant (single organization) app is necessary for successful authentication, as they cannot be authorized via the /common endpoint. Additionally, a developer cannot easily choose to configure an app intended for internal use only as a multi-tenant app to work around this, because multi-tenant apps now require signing up as a Microsoft Partner.

This PR allows new "tenant" config option to be passed to specify a "tenant ID" to use, which is already a supported by the underlying Bing Ads API Python SDK. The config option is entirely optional, and it defaults to "common" to preserve existing behaviour by default ("common" is the value the Bing Ads API Python SDK is already using by default since this tap is currently not providing the optional argument).

Manual QA steps

  • I've successfully used this new option to authenticate a single tenant app.
  • It would be worth someone who is already using it successfully with a multi-tenant app and the /common endpoint testing that it still works for them

Risks

  • I've not added any tests for this new option as I don't normally work in Python and can't see any documentation on running the tests in the README - so didn't spend the time to figure it out (yet). I thought it was best to try contributing this change upstream sooner rather than later though.

Rollback steps

  • revert this branch

Providing the "tenant ID" of a single tenant (single organization) app is necessary for successful authentication, as they cannot be authorized via the /common endpoint.

Additionally, a developer cannot easily choose to configure an app intended for internal use only as a multi-tenant app, because multi-tenant app now require signing up as a Microsoft Partner.

This new config option is entirely optional, and it defaults to "common" to preserve existing behaviour by default.
@singer-bot
Copy link

Hi @robotfelix, thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants