use s3 endpoint config

[rwos]

part of teamhephy/workflow#52

• use the (new) s3 endpoint config value
• and update the docker/distribution fork (see Merging in docker upstream master distribution#2 and Update to current upstream master distribution#1)
• and update the go-dev image

In practice, this depends on teamhephy/workflow#71 (so that the ENDPOINT_FILE is there).

Aside: as for build/distribution - I guess you have some sort of (automated) setup to update this bucket? For our own setup I'm just abusing quay.io (pngmbh@07f7045), just in case you need inspiration :)

[kingdonb]

There is #4 now. I am trying to get a handle on everything that needs to change and what needs to be tested in order for us to put out a new object-storage-cli. (There is also s3-uploader which probably needs to be updated in sync, to support whatever same changes this supports.)

The endpoint configuration is going to be the most useful since it enables off-cloud and bare metal clusters, as well as could be used to nominally add support for digital ocean spaces.

We added support for modern Kubernetes variants, if you want to take a look at this please you are welcome! I've already rebased this in #4 since storage is planned next in our 2.22 release, (or sooner if we can get it handled in a smaller patch.)

If you are not following anymore, please close this and we will follow up with #4.

[rwos]

Hi yeah, sorry, this is severely out of date and I'm not working on it anymore. Closing!