I’m using pulumi, and I’d like to start leveraging the S3 cloud login capabilities. However, our local S3 cloud requires that we provide an --enpoint-url to specify our in-house servers. For example, this is how I would list the contents of a directory:
aws --endpoint-url=<http://internalserver.com> s3 ls --profile internal-profile
Can I configure pulumi in such a way that I can leverage an --endpoint-url override for logging in and storing our stacks?
Does anyone have any insight on this?
Alternatively, is there a way to implement a custom cloud provider for storing stacks? I’d be fine taking that approach as well, assuming I could get some pointers on where to look