Open iamkirkbater opened 5 months ago
Address this issue #71
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
The
gcloud
tool does not seem to have a Darwin arm64 binary available, causingbackplane-tools install all
to fail.Ideally I would like to have behavior that allows me to "best-effort" install all tools for my platform - so that any tools without upstream binaries for a given platform would continue to be installed, and the "errors" turn into warnings. Whether this functionality is behind a flag or the default I don't really have any strong opinions on and can see arguments for both directions.
User flow for the "behind a flag" functionality would look like this:
Without the flag would emit this:
If only emitting a warning and exiting with a success code becomes the default functionality, I'd like to see a flag that negates the effect so that we'd still have the ability to have deterministic builds if this is used somewhere that would explicitly fail it. So that flow would look like this for success:
And with the flag to explicitly fail the install it would look like this:
One important caveat is that I believe this functionality to warn should ONLY apply to binaries that can't be found for a specific architecture - if we can't do some of the auxiliary tasks around building the binary like downloading it (if it's found) or creating a new folder for it to live in then that should error out.