Azure/azure-orbital-integration

TCP to BLOB: Restore support for multiple deployments in same resource group

Closed this issue · 0 comments

Event grid topic and associated subscription are deployed using hard-coded resource names which results in a conflict when attempting to deploy multiple instances of TCP to BLOB within the same resource group. Deploying more than one stack in the same resource group is currently desirable since TCP to BLOB must be deployed in the same resource group as the Orbital spacecraft. To restore this capability, we need to use deployment specific names for grid topic and associated subscription.