Skip to content

Specified query_payload not actually used #35

Description

@fligtar

Thanks for this great library -- saved me a ton of time!

I'm trying to pass in a custom query_payload to FlumeData instead of using the default, and it is properly initialized. However, when the update() call is actually made, the first thing it does it overwrite the query_payload with the default anyway. It seems impossible to actually do a custom query, unless I'm missing something.

Less important, but would also suggest scan_interval not be a required parameter since it should be ignored if a query_payload is passed anyway.

I would submit a pull request but I'm not confident enough in my Python skills. Thanks!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions