John Boxall

1. Regarding `slas:tenant:list` – I agree that this would be useful to have! But the backing API doesn't support it. Right now, the tenant list API endpoint is staff only....

Good points @tobiaslohr – I think it is possible to work around both of these concerns. I agree, let's ship that discussion to a separate issue. With respect to this...

@tobiaslohr / @hnestmann I added unit tests. They're not the best, but significantly better than nothing! I think there is a more you could improve here (eg. adding stdin handling...

> * We should follow the existing patterns for commands, incl. CRUD operations. Therefore for the creation of the new object (like a slas tenant or a client) we should...

To offer an alternative, you can also bridge the current API gap using OCAPI hooks. https://github.com/SalesforceCommerceCloud/ocapi_hooks_collection shows how to do this. 1. It extends the `dw.ocapi.shop.customers.password_reset.afterPOST` to [send a password...

Hey @stm-dschulz, I don't believe a fix can be contributed in the scope of this repo _right now_. Going forward, one of three things will happen: 1. SLAS will add...

Adding onto this, it might be valuable if the devserver had native support for routing proxy requests through a proxy (like MITMProxy). This can be helpful for debugging errors with...

~This approach is likely also blocked by #733.~ Wait – this is only useful for local development, which doesn't have this issue.

Thanks @tobiaslohr. ~Given your answer, my understanding is that **it is not possible to interact with the Sandbox API using an `access_token` provided by `sfcc-ci client:auth`.**~ My new steps are:...

For reference, here is the quick script I ended up with to explore the details of the Sandbox API: https://gist.github.com/johnboxall/7fd92fb8667314ea4d1628fb5229f162