-
Notifications
You must be signed in to change notification settings - Fork 13
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
Expand on the recognised fluxd flags #279
Conversation
Okey doke, as there are old-school |
This adds to the list of fluxd flags that the agent will recognise and include in URLs. Since there are now more than four, and they don't all appear together necessarily, I've changed how the URL is constructed.
- More tests - Don't need struct flag parse annotations
@squaremo I’m happy to merge this it seems to work alright! The code I added is a bit rough wdyt? |
3f618d5
to
3b30570
Compare
We can save the clean-up phase, which reset things to `nil` if they weren't passed as flags, by checking with the flag parser directly. This makes it trickier to construct a config (since it needs the flags parser state), but that's what `ParseFluxArgs` is for. The code that uses ParseFluxArgs is sensitive to whether it gets a `nil`, a value, or an error, so that behaviour must be preserved.
Awesome stuff, thanks @squaremo |
Where are the usage docs for this? |
This adds to the list of fluxd flags that the agent will recognise and include in launch-generator URLs.
Since there are now more than four, and they don't all appear together necessarily, I've changed how the URL is constructed.
Fixes #277. (And needs a compensating change in the service being polled for configs.)