Service Connector Integration

[nturinski]

What is it?

Service Connector helps you connect Azure compute services to other backing services. This service configures the network settings and connection information (for example, generating environment variables) between compute services and target backing services in management plane.

We can leverage this to connect web and container apps to backends such as Storage or Cosmos DB. It will do the connection, can use managed identities (user and system).

Implementation

I propose that we make this a new shared package. The reason being, it seems like the only App Service, Container Apps, and Spring Apps support Service Connector.

We can use this Azure SDK to do the implementation: https://azuresdkdocs.blob.core.windows.net/$web/javascript/azure-arm-servicelinker/2.1.0/interfaces/Linker.html#beginCreateOrUpdate
https://www.npmjs.com/package/@azure/arm-servicelinker

For the UI, it could be another node under either an app service or container app nodes. Underneath that node, we could show something similar to the Portal:

Documentation:

https://learn.microsoft.com/en-us/azure/service-connector/overview
https://learn.microsoft.com/en-us/azure/service-connector/quickstart-cli-app-service-connection?tabs=Using-access-key
https://learn.microsoft.com/en-us/azure/service-connector/quickstart-portal-app-service-connection?tabs=SMI

Supported Regions

Service Connector doesn't support every region. We should have some smart checks to either
a.) only allow creating apps in these compatible locations or
b.) throw an error/disable SC for apps in unsupported locations
https://learn.microsoft.com/en-us/azure/service-connector/concept-region-support