Some other rest sdk's offer up a auth client assist that can help call rest apis that do not yet have a formal cmdlet.
This would be a more generic invoke-webrequest style cmdlet, where your existing auth configuration (env vars/Json) would be used, and users of this new cmdlet would just need to specify verb, payload (if PATCH or POST) and URI to call apis that do not yet have a formal cmdlet.
Ideally this cmdlet would handle getting a bearer token, issuing the HTTP call, and displaying the results.
Bonus points for this cmdlet having an optional flag that could automatically handle cursor/pagination responses (with merging the multi-response lists together into a single list) and single output from the cmdlet.
(I'll admit that last one is a little much, but definitely be cool!)
Some other rest sdk's offer up a auth client assist that can help call rest apis that do not yet have a formal cmdlet.
This would be a more generic invoke-webrequest style cmdlet, where your existing auth configuration (env vars/Json) would be used, and users of this new cmdlet would just need to specify verb, payload (if PATCH or POST) and URI to call apis that do not yet have a formal cmdlet.
Ideally this cmdlet would handle getting a bearer token, issuing the HTTP call, and displaying the results.
Bonus points for this cmdlet having an optional flag that could automatically handle cursor/pagination responses (with merging the multi-response lists together into a single list) and single output from the cmdlet.
(I'll admit that last one is a little much, but definitely be cool!)