-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UpdateSubscriptionAsync method does not update AutoDeleteOnIdle properties #44458
Comments
Thank you for your feedback. Tagging and routing to the team member best able to assist. |
Hey @liangdaxian , are you inquiring about the Azure.Messaging.ServiceBus library? |
@liangdaxian: Please clarify which package and version you're using. |
Hi @liangdaxian. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue. |
hi i think i put it under desc but get trunked: using Azure.Messaging.ServiceBus version="7.17.5" targetFramework="net48" |
I've confirmed that the autoDeleteOnIdle property is defined in the service spec and that the payload is being formatted correctly by the client. This looks to be an issue with the Service Bus ATOM service. @EldertGrootenboer: Not sure why this was transferred over to the client repository, but I'm going to send it back, as it requires service investigation. |
This issue has been transferred to the Azure Service Bus repository for service team investigation as #711. |
Description
i am trying to using the admin api to update some subscription AutDeleteOnIdel time span, code snip as:
var subs = admin.GetSubscriptionsAsync(topicName).GetAsyncEnumerator();
while (subs.MoveNextAsync().AsTask().Result)
{
var subdetails = admin.GetSubscriptionAsync(topicName, subs.Current.SubscriptionName).Result.Value;
}
however the code runs fine but AutoDeleteOnIdle was not actually updated
using
The text was updated successfully, but these errors were encountered: