[#10432] 📝 Apply suggestion.

See https://github.com/backstage/backstage/pull/10528#discussion_r838597752

Signed-off-by: LvffY <louberger@hotmail.fr>
This commit is contained in:
LvffY
2022-03-30 16:20:47 +02:00
parent e0cd63145b
commit 0f290356b9
+4 -1
View File
@@ -75,5 +75,8 @@ _Note:_ the path parameter follows the same rules as the search on Azure DevOps
web interface. For more details visit the
[official search documentation](https://docs.microsoft.com/en-us/azure/devops/project/search/get-started-search?view=azure-devops).
You'll also need to add the [Code Search plugin in your organization](https://marketplace.visualstudio.com/items?itemName=ms.vss-code-search&targetId=f9352dac-ba6e-434e-9241-a848a510ce3f&utm_source=vstsproduct&utm_medium=SearchExtStatus). [More information here](https://github.com/backstage/backstage/issues/10432).
Azure discovery is driven by the Code Search feature in Azure DevOps, this may not be enabled by default. For Azure
DevOps Services you can confirm this by looking at the installed extensions in your Organization Settings. For Azure
DevOps Server you'll find this information in your Collection Settings.
If the Code Search extension is not listed then you can install it from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms.vss-code-search&targetId=f9352dac-ba6e-434e-9241-a848a510ce3f&utm_source=vstsproduct&utm_medium=SearchExtStatus).