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

VS OE: handle service version unavailable gracefully (and maybe try downgrading?) #10167

Closed
dtivel opened this issue Oct 21, 2020 · 2 comments
Closed
Assignees

Comments

@dtivel
Copy link
Contributor

dtivel commented Oct 21, 2020

Use ServiceBrokerExtensions.ReportMissingServiceAsync(...) to report when a requested service version is unavailable.

This is important to do early so that in the future when service versions are removed, older clients with this feature can know that functionality is reduced.

@rrelyea
Copy link
Contributor

rrelyea commented Jan 6, 2021

@dtivel - we'd like to discuss how we should handle situations when we add something to an existing interface that hasn't shipped publicly like: https://github.com/nuget/client.engineering/issues/682
Should we inform test team.
Should we add a call to ReportMissingServiceAsync as this bug discussed when a version is not available.
etc...

@dtivel dtivel modified the milestones: Sprint 182 - 2021.01.11, Sprint 182 - 2021.1.11 Jan 11, 2021
@rrelyea rrelyea removed this from the Sprint 183 - 2021.02.01 milestone Feb 18, 2021
@aortiz-msft
Copy link
Contributor

Bulk-closing VS OE issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants