You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The buildpack builder has a fetcher, which acts as a slug and tar specific network storage system. Its implementation is to store slugs and tars in specific locations on the local filesystem. It appears that the fetcher's goal is to be a fallback in case S3 is not configured for the install.
We're adding support for minio (see Object Storage in deis/deis#4743), which is a more general purpose object storage system that can run in the cluster (currently its implementation is also to store data on the filesystem) in v2 Alpha.
I'm proposing that we remove the fetcher and require that either S3 or Minio access is configured for builder and slugbuilder.
The buildpack builder has a fetcher, which acts as a slug and tar specific network storage system. Its implementation is to store slugs and tars in specific locations on the local filesystem. It appears that the fetcher's goal is to be a fallback in case S3 is not configured for the install.
We're adding support for minio (see
Object Storage
in deis/deis#4743), which is a more general purpose object storage system that can run in the cluster (currently its implementation is also to store data on the filesystem) in v2 Alpha.I'm proposing that we remove the fetcher and require that either S3 or Minio access is configured for builder and slugbuilder.
cc/ @smothiki
The text was updated successfully, but these errors were encountered: