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

Feature request: Additional flags #450

Closed
udf2457 opened this issue Sep 18, 2019 · 5 comments
Closed

Feature request: Additional flags #450

udf2457 opened this issue Sep 18, 2019 · 5 comments

Comments

@udf2457
Copy link

udf2457 commented Sep 18, 2019

Hi,

Would be good to have a few more flags, paricularly the ability to override locations for snmp.yml, generator.yml and mibs/

@brian-brazil
Copy link
Contributor

The mibs location is up to netsnmp. Why do you want to have different paths for the generator files?

@udf2457
Copy link
Author

udf2457 commented Sep 18, 2019

Different paths because I might not be calling generator from the directory. Also there could be use-cases where generator output needs to go somewhere else first before rolling out (e.g. generating alternative configs for test ?)

@tarko
Copy link
Contributor

tarko commented Oct 26, 2019

You can manipulate netsnmp paths with env variables like export MIBDIRS=+/home/tarko/.snmp/alcatel-7750:/home/tarko/.snmp/JuniperMibs before you execute generator

@SuperQ
Copy link
Member

SuperQ commented Oct 27, 2019

I think having flags for the input/output file locations is reasonable, just like having the same flag(s) for the config itself.

@SuperQ
Copy link
Member

SuperQ commented Feb 4, 2024

Fixed in #1028

@SuperQ SuperQ closed this as completed Feb 4, 2024
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

4 participants