You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Shared Image Galleries (SIG) are required to be in the same subscription as the Resource Groups where the agents are deployed. This prevents us from sharing a single SIG across multiple Subscriptions. The current workaround is to create a (SIG) for each subscription, and duplicate the vm versions across them. Ofcourse, this is a wasteful approach.
Scenario: We have multiple Azure Subscriptions, each with its own TeamCity instance. The aim is for each instance to deploy cloud agents within a Resource Group of the Subscription the instance resides in. The neccessary RBAC roles for the managed identity are in place to allow access, but the plugin does not currently pull them due to design (?).
Environment
TeamCity version: --
Azure plugin version: 0.9.1
Diagnostic logs
The text was updated successfully, but these errors were encountered:
Just encountered this one on our TeamCity issue. Indeed plugin lists images available only in the linked subscription and ignored subscription from the configured image (we use kotlin DSL and can configure image from another subscription, but it does not work anyway) so we just observe "Image error" state with some java NSEE.
Description
Currently, Shared Image Galleries (SIG) are required to be in the same subscription as the Resource Groups where the agents are deployed. This prevents us from sharing a single SIG across multiple Subscriptions. The current workaround is to create a (SIG) for each subscription, and duplicate the vm versions across them. Ofcourse, this is a wasteful approach.
Scenario: We have multiple Azure Subscriptions, each with its own TeamCity instance. The aim is for each instance to deploy cloud agents within a Resource Group of the Subscription the instance resides in. The neccessary RBAC roles for the managed identity are in place to allow access, but the plugin does not currently pull them due to design (?).
Environment
Diagnostic logs
The text was updated successfully, but these errors were encountered: