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 login_customer_id config #32

Merged
merged 1 commit into from
Jun 4, 2024
Merged

Conversation

spencerjbeckwith
Copy link

Setting the value of the login-customer-id header to the same value as the syncing customer_id prevents using this tap with a manager account.

This PR makes the login-customer-id header a separate and optional config property (login_customer_id) so manager accounts can be used. If not specified, the login-customer-id header will still be set to the configured customer_id.

@ReubenFrankel
Copy link

Thanks @spencerjbeckwith - this looks good to me. Just wanna test on our side and then we can merge. 🙂

@acarter24
Copy link

acarter24 commented Jun 4, 2024

Very timely, I just got another account added to my manager. Turns out I was setting LOGIN_CUSTOMER_ID in my env but nothing was happening with it! Thanks for this :)

For future improvements, would you consider making customer ids iterable? Or making the tap return all the relevant data for accounts under the manager?

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

Successfully merging this pull request may close these issues.

3 participants