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

Finish Subscriptions #17

Open
goshlanguage opened this issue Oct 5, 2020 · 2 comments
Open

Finish Subscriptions #17

goshlanguage opened this issue Oct 5, 2020 · 2 comments
Assignees
Projects

Comments

@goshlanguage
Copy link
Owner

We should define acceptance criteria for the addition of a service, and adhere our Subscriptions service to this model.

Per our meeting (Oct 5), we've discussed supporting latest API +1 for each service.

We consider completeness as all routes implemented.

@goshlanguage goshlanguage created this issue from a note in Alpha (To do) Oct 5, 2020
@goshlanguage goshlanguage moved this from To do to In progress in Alpha Oct 14, 2020
@goshlanguage goshlanguage self-assigned this Oct 14, 2020
@goshlanguage
Copy link
Owner Author

goshlanguage commented Oct 14, 2020

Big yikes. I believe we have misunderstood the way that Azure SDK versions its APIs. While approaching this for subscriptions, it looks as though the routes are additive, instead of being different versions of the same API routes/functions.

Screen Shot 2020-10-14 at 9 34 59 AM

We may not be able to simply do latest version +1 support. In this example, this would mean not supporting the List route for example.

See: https://docs.microsoft.com/en-us/rest/api/subscription/

@goshlanguage
Copy link
Owner Author

goshlanguage commented Oct 14, 2020

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

No branches or pull requests

1 participant