This cost me a while, so maybe it can help one or the other.<\/p>\n
It seems\u00a0when azure connects to bitbucket (which you\u00a0allow) a new deployment key is created and assigned to the\u00a0repository you want to clone. If\u00a0this repository contains a\u00a0submodule the deployment won’t work as the key which is used for the deployment is not known.<\/p>\n
Fortunately this key is stored in the deployment keys of the original repository (look at the repository settings of bitbucket). You can even see it, but not copy it. What you can do is to write it down (Cumbersome)<\/p>\n
I actually copied it from chrome console<\/p>\n
$(“textarea”).val()<\/p>\n
Now i also know that bitbucket uses jQuery \ud83d\ude42<\/p>\n
Use\u00a0this value (without the hyphens) as\u00a0deployment key for your submodule and you’re ready to go.<\/p>\n
If anyone knows where to find these keys inside azure, please leave me a comment. I’m also happy to hear better ways of doing this,\u00a0but for the moment\u00a0it’s ok.<\/p>\n
Only as a reminder:<\/strong><\/p>\n Create a public key out of the key file:<\/p>\n (This is what most discussions end up with)<\/p>\n (but his worked for me)<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" This cost me a while, so maybe it can help one or the other.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":""},"categories":[88],"tags":[],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":"Harald","author_link":"https:\/\/www.anagram.at\/en\/author\/admin\/"},"_links":{"self":[{"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/posts\/1911"}],"collection":[{"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/comments?post=1911"}],"version-history":[{"count":0,"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/posts\/1911\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/media?parent=1911"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/categories?post=1911"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.anagram.at\/en\/wp-json\/wp\/v2\/tags?post=1911"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}ssh-keygen -y -f mykey.pem > mykey.pub <\/code><\/p>\nssh-keygen -y -f mykey.key > mykey.pub<\/code><\/p>\n