fix: sdk configs api authentication#1634
Conversation
🚫 Missing Linked IssueHi 👋 This pull request does not appear to be linked to any open issue yet. Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically. ✔️ How to fix this
Once linked, this check will pass automatically on your next push or when you re-run the workflow. Thanks for helping maintainers! 🙌 |
XyneSpaces
left a comment
There was a problem hiding this comment.
Reviewing API contract changes for FetchSdkConfigs
33cdb66 to
88f54be
Compare
🚫 Missing Linked IssueHi 👋 This pull request does not appear to be linked to any open issue yet. Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically. ✔️ How to fix this
Once linked, this check will pass automatically on your next push or when you re-run the workflow. Thanks for helping maintainers! 🙌 |
1 similar comment
🚫 Missing Linked IssueHi 👋 This pull request does not appear to be linked to any open issue yet. Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically. ✔️ How to fix this
Once linked, this check will pass automatically on your next push or when you re-run the workflow. Thanks for helping maintainers! 🙌 |
Type of Change
Description
/sdk/configsapi. The api now supports bothclientSecretandsdkAuthorization. Corresponding BE PR (currently deployed on integ): feat(core): added sdk authorisation support to sdk configs hyperswitch#12887How did you test it?
clientSecretinHyperElements.options. Got200api response.sdkAuthorizationinHyperElements.options. Got200api response.Checklist
npm run re:build