We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
While using honey with a config file, the backend name displayed in the results table isn't the one defined in the config.
honey
backend name
For example, say I have the following config:
{ "example-gcp": { "projects": "proj-1,proj-2,proj-3", "type": "gcp" } }
And running a search produces the following table (details obscured for privacy):
$ honey -b example-gcp -f my-instance +---------------------+--------------+----------------------+--------------------+---------+--------------+---------------+ | ID | BACKEND NAME | NAME | TYPE | STATUS | PRIVATE IP | PUBLIC IP | +---------------------+--------------+----------------------+--------------------+---------+--------------+---------------+ | xxxx | gcp | xxxx | n1-standard-4 | RUNNING | x.x.x.x | x.x.x.x | | xxxx | gcp | xxxx | custom-2-16384-ext | RUNNING | x.x.x.x | x.x.x.x | +---------------------+--------------+----------------------+--------------------+---------+--------------+---------------+
I would expect the backend name column to speficy the configured backend name (example-gcp) and not the backend type (gcp)
example-gcp
gcp
The text was updated successfully, but these errors were encountered:
#5 show custom backend name
f5fcfae
Merge pull request #6 from bringg/custom_backend
8b3048a
No branches or pull requests
Hi,
While using
honey
with a config file, thebackend name
displayed in the results table isn't the one defined in the config.For example, say I have the following config:
And running a search produces the following table (details obscured for privacy):
I would expect the
backend name
column to speficy the configured backend name (example-gcp
) and not the backend type (gcp
)The text was updated successfully, but these errors were encountered: