misc: Use external_id instead of customer_id and subscription_id #419
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.
Context
We want to clarify the difference between lago ids and external ids.
Today, we have
customer_id
on customers andsubscription_id|unique_id
on subscriptions.On the API, the goal is to use external_ids:
external_id
orexternal_customer_id
for customerexternal_id
orexternal_subscription_id
for subscriptionDescription
The goal of this PR is to:
customer_id
toexternal_id
on customerssubscription_id
toexternal_id
on subscriptionsunique_id
from subscriptions