different ssh key per entreprise
Asked by J?r?me Godbout:

I already took a look at this post:

<https://confluence.atlassian.com/bbkb/multiple-ssh-keys-settings-for-different-bitbucket-cloud-accounts-1168847503.html>

But this fall very shortcoming if you use a package manager and the url are not editable on the fly. We do work with other entreprise, we have our own bitbucket and they have their. The git config fake domain work when doing a simple git clone from cli. But when using tools that automate the packages building, work across cie is a nightmare with bitbucket.

Can we have subdomain like gitlab please

    gitlab.my_company.com

That would make this viable into a git config

or mycie.bitbuckt.org/ would be nice, it can redirect under the hood to bitbucket.org/mycie/ so you infra can still work but we could at least make a config that doesn't change the source to support multiple entreprise or cross entreprise repository with packages managers. having to duplicate branches between entreprise on bitbucket only for working is a huge pain.

Wish our management finally approve our request to move to gitlab or github, bitbucket is full of limitation compare to other offering.


Answers:
author: Patrik S
body: Hey [@J?r?me Godbout](/t5/user/viewprofilepage/user-id/1437516) ,

thank you for reaching out to Community!

In the article that you shared there are two different suggested workaround:

* ++Workaround 1++: having different .gitconfig based on the top-level folder
* ++Workaround 2++: editing the SSH config file to have a "fake" domain

I understand that Workaround 2 would involve modifying the URL you point to in your dependencies, so that wouldn't be an option for you. But maybe Workaround 1 would work for your use-case, as it's solely based on the directory where the command is being executed. Many package tools use Git commands under the hood, so they should usually respect the `.gitconfig` file when executing a git operation.

However, this very depends on how the tool implements the fetch from git repositories, so it's important to to check the documentation for each specific tool you're using to ensure compatibility and to see if any additional configuration is necessary.

As for the custom domain, while it's still not available in Bitbucket Cloud, we already have a feature request with our development team to implement this functionality, which you can access in the following link :

* <https://jira.atlassian.com/browse/BCLOUD-21517>

I would recommend adding your Vote to that feature, as it helps our product managers and engineering team understand the demand for new features. To keep up to date with that feature's progress, you also have the option to add yourself as a watcher, so you will be notified by email of any new comment/update on that ticket. Please note that all features are implemented with [this policy](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) in mind.

Thank you, [@J?r?me Godbout](/t5/user/viewprofilepage/user-id/1437516) !

Patrik S

comments: author: J?r?me Godbout
body: Both workaround are only valid for local checkout, this does help when using package manager or any other form of automated tools.


Tags: bitbucket-cloud

cloud