-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: add EU host support [DANTE-1574] #908
Conversation
}: CreateClientParams & { sequenceKey: string }) => { | ||
const config = loadRuntimeConfig() | ||
|
||
const { cmaHost, cdnHost } = getHosts(host || config.host || 'api.contentful.com') |
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.
Do I understand it right that create
only uses CDA while apply
only uses CMA? It feels a bit weird then to pass api.contentful.com
to both. Could we use a similar pattern here as we do with the token and have separate cmaHost
and cdaHost
params?
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.
so yes, create uses CDA and apply uses CMA, but in the current setup, we just create an API client that has access to both, I wouldn't necessarily want to change that right now although I see your point that it's not needed to have both APIs for both use cases
🎉 This PR is included in version 2.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Allow user to pass a
--host
parameter, this then will set CDA and CMA clients to use either US or EU APIs