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

REST Endpoint to enable and disable direct commits. #12

Open
at3560k opened this issue Jul 9, 2015 · 3 comments
Open

REST Endpoint to enable and disable direct commits. #12

at3560k opened this issue Jul 9, 2015 · 3 comments

Comments

@at3560k
Copy link

at3560k commented Jul 9, 2015

Do you have a rest/other API available to query, and toggle the "disable direct commit" option?

@mdavoodi
Copy link
Contributor

Currently there isn't a rest API endpoint to do this. If there's more support for this, we can add it in the future.

@mdavoodi mdavoodi changed the title Question/Feature Request REST Endpoint to enable and disable direct commits. Jul 13, 2015
@javaerb
Copy link

javaerb commented Aug 14, 2015

Would love to hear the use case. Is this just to work around a limitation?

@at3560k
Copy link
Author

at3560k commented Aug 14, 2015

RE: limitations -- it's more a limitation of the stash APIs, whereas there is no apparently no API to generically administer plugin fields.

For the use case:

Imagine an instance of stash with a few thousand repositories, where about 90% are centrally administered by a program/proxy/agent (instead of a human). No human is permitted/has permissions to modify the settings of these repositories.

In the case of this plugin, it is desirable to expose the enable/disable setting to the business owner of the repository (but not the remainder of the repository settings, such as branch protection, readers/writers, etc). Without an API -- the proxy/agent has to resort to brittle behaviours to modify this setting.

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

No branches or pull requests

3 participants