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

Not reading all the options in config file #39

Open
titansmc opened this issue Mar 29, 2022 · 5 comments
Open

Not reading all the options in config file #39

titansmc opened this issue Mar 29, 2022 · 5 comments

Comments

@titansmc
Copy link

hi,
I am using the RC2 and it doesn't read keyring and follow options asI have them here:

[node:default]
host=graylog.domain.com
tls=True
port=
endpoint=/api/
username=user
keyring = True
follow = True

Also, since my graylog server is running on 443, I had to leave it empty, otherwise it is malforming a URL like graylog.domain.com

@valentin-krasontovitsch
Copy link
Collaborator

so sorry about the late reaction - I have to admit I've never worked with a keyring, I'm gonna have to try and reproduce this and see what happens. if you could give me a simple recipe on how to setup a keyring, I would really appreciate that (also - do i have to use gnome for the keyring thingy to work?)

i'm not sure I follow your last comment, about the port - you had to leave the port option empty? if you write 443 there, it get's messed up? gonna check that out!

just give me a few more days please, hopefully i will find some time to look at this.

@titansmc
Copy link
Author

titansmc commented Jun 9, 2022

I am using gnome keyring. So if you use bonfire with -k option, it should ask you for your keyring passphrase so it will store it there, and next time you don't need to type the password (as long as the keyring is unlocked).
So at this moment I need to type:
bonfire -f -k :hpc
and I cannot have the -k and -f options defined at the config file like:

[node:default]
host=graylog.domain.com
tls=True
port=
endpoint=/api/
username=user
keyring = True
follow = True

so I would like to be able to execute:
bonfire :hpc
and that is it, everything else should be in the config file.

Forget about the port, it looks fine.

Cheers.

@valentin-krasontovitsch
Copy link
Collaborator

alrighty i'm finally looking at this.

  • follow mode is not read from config file, it can only be triggered from the command line. but it's not difficult to implement that option
  • happy to hear that the port thingy seems to be working

gonna look at the keyring next - do i understand correctly that it works fine when you use the command line option, the only problem is that you cannot supply it in the config file, and you would like to be able to do that?

@valentin-krasontovitsch
Copy link
Collaborator

and would you like to supply the keyring option on a node to node basis, or should we add a new general section (or some such name), where one could set the keyring option and it would be respected for all nodes / all queries?

@titansmc
Copy link
Author

titansmc commented Oct 7, 2022

sorry, you caught me on vacation.
Both would work for me, although I always use -f option. So if you ask me, I would probably do it at the general section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants