Skip to content

allow verbose parameter on getNetworkEvents - #204

Closed
bk2zsto wants to merge 1 commit into
meraki:mainfrom
bk2zsto:main
Closed

allow verbose parameter on getNetworkEvents#204
bk2zsto wants to merge 1 commit into
meraki:mainfrom
bk2zsto:main

Conversation

@bk2zsto

@bk2zsto bk2zsto commented Mar 5, 2023

Copy link
Copy Markdown

In Meraki Case # 09285978 I was advised to add verbose=True to my getNetworkEvents call in order to get aid included in association events. It is appended to the event in the extraData key.

Its not documented in the OpenAPI spec but I'd like to get rid of my local fork for making this work. If I need to fork the OpenAPI repo and add it there I can do that too.

Guessing verbose is available for lots of other methods but not sure where to start determining that.

@andy-shady-org

Copy link
Copy Markdown
Contributor

This MR removes the patch that was applied for request exceptions what was fixed in #202

@TKIPisalegacycipher

Copy link
Copy Markdown
Collaborator

Hi @bk2zsto we've long made the strategic decision to not complicate this library by hacking undocumented attributes or parameters into the library. If you would like to see it added here, please reach out to Meraki Support and/or your account rep and open a feature request.

If Meraki chooses to officially document this attribute, then the subsequent library release will include it.

Thank you @andy-shady-org as well for calling out the reversion of #202.

For now, I will close this PR.

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

Successfully merging this pull request may close these issues.

3 participants