Skip to content
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

Backend name isn't showen properly when using a config file #5

Closed
hagaibarel opened this issue May 24, 2021 · 0 comments
Closed

Backend name isn't showen properly when using a config file #5

hagaibarel opened this issue May 24, 2021 · 0 comments

Comments

@hagaibarel
Copy link

Hi,

While using honey with a config file, the backend name displayed in the results table isn't the one defined in the config.

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)

Shareed2k added a commit that referenced this issue Jun 21, 2021
Shareed2k added a commit that referenced this issue Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants