getServiceEndpoints missing in 8.*.*

[grawcho]

Environment

Node version: v10.15.3
Npm version: 6.9.0
OS and version: linux (fedora 28 kernel 5.0.16
azure-devops-node-api version: 8.1.0

Issue Description

i'm using azure-devops-node-api to rotate secrets in service endpoints from script and tried to upgrade from 7.2.0 to 8.1.0 and geterviceEndpoints / updateServiceEndpoints is missing from the TaskAgentAPIBase.d.ts

Expected behaviour

all functions in older version have backward compatibility

Actual behaviour

functions are missing from the mpn package

Steps to reproduce

1. install azure-devops-node-api@8.1.0
2. try calling agentapi.getServiceEndpoints(projec.id)
3. error TS2339: Property 'getServiceEndpoints' does not exist on type 'ITaskAgentApiBase'.

[stephenmichaelf]

@grawcho There can be breaking changes across major versions of the lib.

[damccorm]

I'm going to close since this is expected behavior. We guarantee back-compat for minor/patch updates, but not for major version updates

[grawcho]

What could be a possible solution?

…

On Wed, May 29, 2019, 23:39 Danny McCormick ***@***.***> wrote: I'm going to close since this is expected behavior. We guarantee back-compat for minor/patch updates, but not for major version updates — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#317?email_source=notifications&email_token=AA2KHW3BUV7UNNN4MN5CZWTPX3SWTA5CNFSM4HQQMFOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQSLGI#issuecomment-497100185>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2KHWYA4Y6AORKVW5HKNMLPX3SWTANCNFSM4HQQMFOA> .

[damccorm]

In the short term, you can hit the endpoint directly - https://docs.microsoft.com/en-us/rest/api/azure/devops/serviceendpoint/endpoints/get%20service%20endpoints?view=azure-devops-rest-5.0

Longer term, it looks like this has been moved into its own API, we should hopefully be able to generate it for this library soon as well - see #310. It might be worth adding this request in the developer community as well. That way it gets routed to the endpoint owners, and if implemented will eventually end up here as well when we regen.