Skip to content
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

Using QueueMetadata fields to represent different data and types #97

Open
plameniv opened this issue Apr 21, 2020 · 0 comments
Open

Using QueueMetadata fields to represent different data and types #97

plameniv opened this issue Apr 21, 2020 · 0 comments
Labels
bug Something isn't working M-azure This issue is related to the Azure module P2 Priority 2
Milestone

Comments

@plameniv
Copy link
Collaborator

We are using QueueMetadata.VisibilityTimeout to pass in the number of seconds for the visibility timeout and to return the timeNextVisible date in the format of "Tue, 21 Apr 2020 16:33:23 GMT"

Similarly we are using QueueMetadata.TimeToLive to pass in the number of seconds for a message’s time to live and to return the expirationTime date in the format of "Tue, 21 Apr 2020 16:33:23 GMT"

We should instead add QueueMetadata.TimeNextVisible and QueueMetadata.ExpirationTime.

This can potentially break downstream users if they use the current metadata to access timeNextVisible and expirationTime.

@plameniv plameniv added bug Something isn't working M-azure This issue is related to the Azure module labels Apr 21, 2020
@plameniv plameniv added this to the 1.3 milestone Apr 21, 2020
@sklose sklose modified the milestones: 1.3, 1.4 Oct 13, 2020
@plameniv plameniv added the P2 Priority 2 label Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working M-azure This issue is related to the Azure module P2 Priority 2
Development

No branches or pull requests

2 participants