dpogorzelski/speedrun

Control your compute fleet at scale

Hi there 👋

What I'm currently working on

Projects I worked on

speedrun's Issues

Do not print stdout/err content by default

A run should print only the run summary by default and only print output if required via flag

Support fully ephemeral ssh keys

Group successes and errors together for non streaming outputs

Add Homebrew formula

There shall be a formula

Allow for ephemeral key to be removed from metadata after each run

Implement a fancy progress update for every step with spinner during progress and ok tick when done, failures should have red X and print log underneath

bastion host support

ProxyCommand

Allow to set project/instance level keys

Supply your own key pair from disk

Allow to only output result of failures (flag/config)

Support OsLogin in GCP

Key new should confirm key creation

Indicate how much time it took for each step

Find target instances via consul service discovery

Help should only be printed on wrong usage

• returning an error should not cause the help to be printed
• the error is reported twice in some cases, once by log library and once by cobra on exit, should be only one instead

Error: Couldn't initialize GCP client (Compute): google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Usage:
  speedrun key set [flags]

Examples:
  speedrun key set 
  speedrun key set --filter "labels.foo = bar AND labels.environment = staging"

Flags:
      --filter string   Set the key only on matching instances
  -h, --help            help for set

Global Flags:
  -c, --config string     config file (default "$HOME/.speedrun/config.toml")
  -l, --loglevel string   Log level (default "info")

⨯ Couldn't initialize GCP client (Compute): google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.

Config file is not found on windows

Detect first run and have a small wizard where you ask for project id, save it to the config file in .executor/config (toml)

Allow time based key expiry of keys

It should be possible to span commands across multiple GCP projects

Whitelist firewall access automatically

Sign Mac binaries

Currently Mac builds are not signed which produces a security warning

When launching a command on a large number of instances everything hangs

Add a "cp <src> <dest>" command that performs scp of files

It should be possible to copy files to/from instances

Add the ability to stream output

Implement a progress indicator

Add support for AWS service discovery

As per title

Allow to use internal IPs

It should be possible to connect to instances via their private IP instead of public one

Handle interactive commands

some commands like sudo apt install dnsutils will wait for user input to confirm the action.
try to catch runs stuck waiting on user input and return immediately

The output should print the instance name instead of it's public IP

If the private key is removed execution fails because it tries to load a non existing key form disk

Implement a filtering mechanism that is provider agnostic

Current --filter option uses GCP native filter (https://cloud.google.com/sdk/gcloud/reference/topic/filters)
This should be re-evaluated and adapted to provide a single consistent filtering experience across vendors

Sometimes the output is not padded correctly

✓ Running [sudo apt-get install -qq jq dnsutils]
  hostname:
    Selecting previously unselected package libonig5:amd64.
(Reading database ... 42029 files and directories currently installed.)
    Preparing to unpack .../libonig5_6.9.1-1_amd64.deb ...
    Unpacking libonig5:amd64 (6.9.1-1) ...
    Selecting previously unselected package libjq1:amd64.
    Preparing to unpack .../libjq1_1.5+dfsg-2+b1_amd64.deb ...
    Unpacking libjq1:amd64 (1.5+dfsg-2+b1) ...
    Selecting previously unselected package jq.
    Preparing to unpack .../jq_1.5+dfsg-2+b1_amd64.deb ...
    Unpacking jq (1.5+dfsg-2+b1) ...
    Setting up libonig5:amd64 (6.9.1-1) ...
    Setting up libjq1:amd64 (1.5+dfsg-2+b1) ...
    Setting up jq (1.5+dfsg-2+b1) ...
    Processing triggers for man-db (2.8.5-2) ...
    Processing triggers for libc-bin (2.28-10) ...

Success: 1 Failure: 0 Error: 0

Version should be injected via linker flags

Broken progress output

The progress output is broken when log messages about new fingerprints is present