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
Currently, although certs:attach <cert> <domain> will properly error out if <cert> is bogus/non-existent, it doesn't if <domain> is similarly non-existent. Consider the following unit test, which is currently failing (err is nil):
if err := Attach(&client, "test-example-com", "non-existent.domain.com"); err == nil {
t.Fatal("An Error should have resulted from the attempt to attach a valid cert to a non-existent domain")
}
This issue tracks work on the client side, and deis/workflow#475 tracks server-side work
From @arschles on March 15, 2016 23:35
Currently, although
certs:attach <cert> <domain>
will properly error out if<cert>
is bogus/non-existent, it doesn't if<domain>
is similarly non-existent. Consider the following unit test, which is currently failing (err is nil):This issue tracks work on the client side, and deis/workflow#475 tracks server-side work
Copied from original issue: deis/workflow-cli#24
The text was updated successfully, but these errors were encountered: