We have had quite some succes setting up queue's, topics and subscriptions in terraform matching the expectations of rebus. But recently a new app service started to fail on startup because Rebus tries to update a subscription that it should not. Turns out that the management client for some reason now returns an https uri for the forward queue where Rebus constructs it with http.
I've no idea what has happened or changed. There is no scheme mentioned in the configuration and when querying the subscriptions with az cli they all look the same.
Update: when I create the subscription from the portal I get the same result: the forward queue has an https uri scheme.
We have had quite some succes setting up queue's, topics and subscriptions in terraform matching the expectations of rebus. But recently a new app service started to fail on startup because Rebus tries to update a subscription that it should not. Turns out that the management client for some reason now returns an https uri for the forward queue where Rebus constructs it with http.
I've no idea what has happened or changed. There is no scheme mentioned in the configuration and when querying the subscriptions with
az cli
they all look the same.Update: when I create the subscription from the portal I get the same result: the forward queue has an
https
uri scheme.