Philip Lombardi
Philip Lombardi
``` plombardi@plombowski ~/w/scout> forge deploy --dry-run Traceback (most recent call last): File "/usr/local/bin/forge/.bootstrap/_pex/pex.py", line 365, in execute File "/usr/local/bin/forge/.bootstrap/_pex/pex.py", line 293, in _wrap_coverage File "/usr/local/bin/forge/.bootstrap/_pex/pex.py", line 325, in _wrap_profiling File...
I was attempting to reproduce https://github.com/datawire/forge/issues/125 and I wanted to get the output from `/tmp/forge.log` but the output was never written to the log file.
Kubernaut backend has a number of test layers and Forge makes it difficult to test all of them: 1. func tests for things like API request / response parsing and...
`forge deploy` is a potentially dangerous command. If you run it off the wrong branch and are not paying attention then it can deploy a whole new set of code....
We've had requests for alternative Docker tags compared to Git hash identifiers in the past. One solution would be to detect when building from a tag to generate a version...
It would be nice if we could control the size of Git hashes. It's very rare to need the full thing. I think Git by default picks "7" as unique...
Take a look at the output below... I was logged into my Docker daemon as `d6eautomaton` but told Forge to use my `plombardi89` credentials. Forge couldn't authenticate so it isn't...
Right now Forge always prompts for username/password for a Docker registry. There is a better way and it would allow us to remove the base64 encoded password from `forge.yaml`. Docker...
``` [plombardi@localhost devops-days-boston]$ forge setup == Checking Kubernetes Setup == CMD: command failed[1]: Client Version: v1.7.4 The connection to the server localhost:8080 was refused - did you specify the right...
Seems to be an intermittent issue where a fabric VPC will fail to delete when a user deletes and then recreates a fabric. Usually the issue is the Internet Gateway...