gravitational
Current Force blockers/requirements
~- support for setting/keeping environment variables over SSH connections~ ~- native S3 upload module (not strictly a blocker but definitely a nice to have, could always just use a container with awscli installed)~ ~- ability to mount a local temporary directory on disk or some kind of force-wide storage which is accessible by all commands (for temporary artefact storage, copying out of build containers and uploading to S3 - may already be possible)~ - all jobs will upload artefacts straight to S3 for isolation
~The other thing I was thinking about is that for the S3 integration, we'll also likely need a way to reference files inside of a container for upload, or maybe to copy files from a container's ilesystem to a Force TempDir() so that the S3 uploader can find them. This is initially why I was asking about shared storage.~
~At the moment I'm unsure how I should reference files that have been built inside a container as they will currently be thrown away when the build job finishes.~ - no longer needed, we will do this with multi-stage Docker/buildkit builds using a force container
~Something that would be very nice with S3 is a way to iterate over and upload all files in a directory. Either as part of the S3 plugin or as a looping concept within Force itself.~
https://github.com/gravitational/force/issues/75
Not really a blocker currently, but will be needed to make the build process faster when packaging works.