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

Bitbucket Server - Different api-path parameters other than Bitbucket Cloud are not documented #660

Open
cx-scord opened this issue Feb 25, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@cx-scord
Copy link
Contributor

Description

The api-path field for Bitbucket Server isn't usually "2.0" like it's described in all application.yml resources or in the wiki documentation examples and descriptions, it (usually) has to be redefined to be empty or a single path /, so one won't receive a 404 error like this HttpClientErrorException$NotFound: 404.

Expected Behavior

Having documented in Bitbucket's Configuration section the differences when setting the api-path parameter between Bitbucket Cloud and Server, for Bitbucket Server there should be a statement on how to set the api-path, like simply using an empty parameter or having only the initial path's backslash like api-path: / or any other applicable options.

Actual Behavior

No documentation stating the differences between the API versions and paths on Bitbucket Cloud and Server. When leaving the /2.0 on the api-path for a Bitbucket Server, a 404 error will be received, but only when debugging we see the URL looks like https://<Bitbucket URL>/rest/api/1.0/2.0/ and the /2.0 shows up after the /1.0.

@cx-scord cx-scord added the bug Something isn't working label Feb 25, 2021
@cx-scord
Copy link
Contributor Author

cx-scord commented Mar 2, 2021

After speaking with @jbrotsos I'll produce a PR with these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant