Skip to content

Issue #1981: REST API Design: Account specific Extensions Configuration REST API might need to be decoupled #2127

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.

Sign up for GitHub

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

Jump to bottom
Open
abdulazizali77 opened this issue May 4, 2017 · 0 comments
Open

Issue #1981: REST API Design: Account specific Extensions Configuration REST API might need to be decoupled #2127

abdulazizali77 opened this issue May 4, 2017 · 0 comments
Assignees
@gvagenas @abdulazizali77

Comments

@abdulazizali77
Copy link
Contributor

Currently the Account specific Extensions Configuration REST API is tightly coupled to the Extensions Configuration REST API.
What differentiates the Account specific and global Extensions Configuration REST API is the existence of the accountSid parameter.
@abdulazizali77 abdulazizali77 changed the title Issue #1981: Design: Account specific Extensions Configuration REST API might need to be decoupled Issue #1981: REST API Design: Account specific Extensions Configuration REST API might need to be decoupled May 4, 2017
@abdulazizali77 abdulazizali77 mentioned this issue May 6, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gvagenas gvagenas

@abdulazizali77 abdulazizali77

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gvagenas @abdulazizali77