The subscription ID for an SRE is set in the configuration file.
When and SRE is deployed, this is written to the projects hash map in pulumi.yaml in Azure storage (I believe this is the equivalent on pulumi.stack.yaml for local storage).
If you change the subscription ID in the configuration, the remote value is not updated.
We could,
Update this value and allow changing an SRE's subscription
(This would likely mean deleting and recreating most or all of the resources)
Prevent moving subscriptions
In which case, we shouldn't give users the option to change this configuration value
JimMadge
commented
2 hours ago
The subscription ID for an SRE is set in the configuration file. When and SRE is deployed, this is written to the
projectshash map inpulumi.yamlin Azure storage (I believe this is the equivalent onpulumi.stack.yamlfor local storage).If you change the subscription ID in the configuration, the remote value is not updated.
We could,