-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inspec compliance login* should support a hostname for the SERVER argument #1473
Comments
For solution see #1471 |
Another error in the same category discovered by @billmeyer
|
arlimus
added a commit
that referenced
this issue
May 30, 2017
Non-url URIs may have lead to broader crashes than initially fixed. Overwrite all URL resolvers in the plugin to work with these non-schema URLs. Fixes #1473
arlimus
added a commit
that referenced
this issue
May 30, 2017
Non-url URIs may have lead to broader crashes than initially fixed. Overwrite all URL resolvers in the plugin to work with these non-schema URLs. Fixes #1473 Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
aaronlippold
pushed a commit
to aaronlippold/inspec
that referenced
this issue
Jun 8, 2017
Non-url URIs may have lead to broader crashes than initially fixed. Overwrite all URL resolvers in the plugin to work with these non-schema URLs. Fixes inspec#1473 Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
inspec compliance login SERVER and inspec compliance login_automate SERVER don't specify if SERVER argument is a hostname or a URL. When using a hostname, the login will fail with an exception (see below).
InSpec and Platform Version
1.7.2
Replication Case
$ inspec compliance login chefcompliance01.billmeyer.corp --insecure --user='bmeyer' --token='eyJh...qqpQ'
Possible Solutions
Accept either a hostname or a URL.
Stacktrace
Please include the stacktrace output or link to a gist of it, if there is one.
The text was updated successfully, but these errors were encountered: