seanaty Atlassian Team

It could be the top right if you're looking at the horizontal navigation. Here is a direct link to the page where you can create the app password: https://bitbucket.org/account/settings/app-passwords/

If you are seeing "The requested repository either does not exist or you do not have access. If you believe this repository exists and you have access, make sure you're authenticated." it's likely that you're getting either a 404 or 403 response and not a 200. (adding -v to curl will let you see all the headers including…

Try going to this page: https://id.atlassian.com/manage-profile/account-preferences More information on account deletion here: https://support.atlassian.com/atlassian-account/docs/delete-your-atlassian-account/

401 means that you are unauthenticated. The problem is with your authentication, as you guessed. An app password is not a Bearer token, you still need to provide your Bitbucket username like this: --user 'my-username:my-app-password' I was curious about the --user param and checked to see what header curl was using with it…

it still doesn't return any data. Is it an empty JSON object? A page object with zero items? Is there an HTTP status code? I'm sure the request is returning some type of data that would be useful for diagnosing. My guess is the issue is how you're creating the request in curl. Here is the documentation I'm seeing for the…

Work around is to make 2 API calls. Use the branch API to get the current commit of that branch, then use the current commit to call the source API.

Unless the behavior changed since the a last time I came across this, invitation emails are not sent ever. The onus is on the admin to email their users and instruct them to go through a password reset flow.

It's likely that you're either not authenticated or you're authenticated as someone else who doesn't have access to these repositories. I would double check on these things.

I think this answers most of your questions: https://community.atlassian.com/t5/Bitbucket-Pipelines-questions/Services-end-of-Support/qaq-p/1852862#M5819 Services and webhooks basically do the same thing (one reason we are getting rid of services). It's hard to say what will break because it depends on what the service or…

At the moment I don't think what you're asking for is possible. I think that if merge restrictions were more specific then you could do this. Here is the public issue requesting that: https://jira.atlassian.com/browse/BCLOUD-21205 e.g. let's say you want to ran builds A, B and C but only A and B are required to pass. Today…

You don't want to use x-token-auth with app passwords. Replace that with your username. Also, if that's your real app password you should delete it and create a new one. https://support.atlassian.com/bitbucket-cloud/docs/clone-a-repository/

Unfortunately this is a known issue in that this page times out for large teams. I suggest watching/voting for this public bug: https://jira.atlassian.com/browse/BCLOUD-17803 As a work-around you can check the permissions for each repository individually with this…

The link you reference is for Bitbucket Server but the screenshot you shared is from Bitbucket Cloud. To clone through HTTPS Bitbucket Cloud recommends what's called an "app password" (because it can also be used to make requests to the Bitbucket API). You can see the link to "App passwords" in your screenshot. Create one…

It's likely you need to percent-encode the curly brackets {} which are %7B and %7D respectively. Without encoding: % curl 'https://api.bitbucket.org/2.0/repositories/atlassian/{5137f783-a12b-4958-a614-4a2af63fca20}' | jq . { "type": "error", "error": { "message": "The requested repository either does not exist or you do…

Correct. No need to migrate a repository. Just need to create a new webhook if you want it to keep operating. Please note that not all services are still working. It all depends on the service that you're using. Of course the POST service is generic.

If you're looking for a public repository, the Software Heritage graciously archived all the public repositories and made them available here: https://bitbucket-archive.softwareheritage.org/ If you're looking for a private repo then you'd have to go through support. EDIT: Looks like it's available…

If you don't see the settings it means the user you are currently logged in as is not an admin of the workspace. Could it be you have multiple accounts?

Bitbucket username.

@Blaine Trimmell You can create an app password in that case.

The link at the top is queued to be deployed. If you're using git with SSH then you don't need to do anything.

Git push/pull will continue to work always. It's foundational to what we do :) There are 2 ways to git push/pull today: * SSH * HTTPS If your repository is already set up for SSH then you don't need to do anything. If your repository is set up to use HTTPS then you'll need to create and app password and update your git…

This change is only affects Bitbucket Cloud.

No. Relevant thread here: https://community.atlassian.com/t5/Bitbucket-questions/What-does-end-of-support-for-passwords-mean-for-me/qaq-p/1851002 Really concise explanation: You current Atlassian PW will only work for logging into the web UI. Any other auth (API, git over HTTPS) will require you to create a new app…

> But then I went to one of our oldest repos (made a LONG time ago) and, behold, there IS a "Services" option in the Repository Settings under Workflow. The feature was soft-deprecated in 2019. Effectively making it such that no one could add a new service and also hiding the "Services" section in the UI unless a…

@Ruhan Coetzer Your link doesn't work and the documentation hasn't been updated. Indeed it doesn't! It worked when I posted it but I've tracked its disappearance down to a documentation migration that just happened. On the plus side, I hope you'll be happy to hear that we are investing in our documentation. I'll get it…

Do you have a link to the page where that documentation is from for reference?

For reference, here is a link to the announcement: https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-password-authentication/ What this means is that Atlassian passwords will only let you interactively log into Bitbucket (e.g. via the Bitbucket.org website in a browser) as well as other Atlassian products.…

Bitbucket doesn't have an API to display the number of installations, unfortunately. The best way to sync or check if a user has uninstalled (if you missed the callback) would to make a request to an endpoint that requires authentication. If you get a 401 back, this would mean that the application has been uninstalled. Be…

It's probably best in this scenario to contact support and they can set you straight. I doubt there is anything you can do (that you haven't already tried) on your end. You could potentially try deleting the repository via the API and see if that'll…

Yes this is available. This is called "merge checks." You can specify different rules that have to be satisfied before being able to be merged to master. For instance you can require that in order to merge in to master people can only do so through a pull request. You can also specify that it has to have specific users'…