-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix type of 'PerfScore' in ResponseApplianceGetDeviceAppliancePerformance #43
Closed
tommyers-elastic
wants to merge
153
commits into
meraki:main
from
tommyers-elastic:42-fix-get-device-appliance-performance
Closed
Fix type of 'PerfScore' in ResponseApplianceGetDeviceAppliancePerformance #43
tommyers-elastic
wants to merge
153
commits into
meraki:main
from
tommyers-elastic:42-fix-get-device-appliance-performance
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Manually initiated code generation workflow for Meraki Dashboard OpenAPI specification (v1.26.0)
Manually initiated code generation workflow for Meraki Dashboard OpenAPI specification (v1.27.0)
Adds retry and backoff logic to HTTP client based on "retry-after" header.
Split Github actions workflow into two jobs: 1) Version check if a client needs to be generated 2) Generate new client with git tag/release Moved templates into .github folder, and deleted the build folder/files. removed .gitignore from repo.
Adds a new version matching condition to prevent commits such as this one from triggering a client generation build step.
Update GitHub Actions
Retrieve a list of organizations.
Update and move the code generator documentation.
Revert "New main branch SDK doesn't use the intended user agent strin…
Refactor api client to adhere to rate limits
- New main branch SDK doesn't use the intended user agent string format meraki#21 - Incorrect links to documentation in code meraki#23 [Removed] - API Rate limiting is not handled in client meraki#20 - Refactor api client to adhere to rate limits meraki#25 - `AccessPolicyNumber` was absent in response structs of `ResponseSwitchGetNetworkSwitchAccessPolicy` and `ResponseItemSwitchGetNetworkSwitchAccessPolicies`.
Develop v2.0.9
- dashboard-api-go supports now v1.44.1 of Meraki Dashboard API. - User-agent is now required. Format of string "ApplicationName VendorName".
## [3.0.0] - 2024-04-16
### Changed - `ResponseItemNetworksGetNetworkGroupPolicies` add new attribute `Name`. - `ResponseNetworksGetNetworkSyslogServersServers` change `Port` to string. - `ResponseNetworksUpdateNetworkSyslogServersServers` change `Port` to string.
## [3.0.1] - 2024-05-22
### Changed - `ResponseItemSwitchGetNetworkSwitchAccessPolicies` add new attribute `AccessPolicyNumber`. - `ResponseSwitchGetNetworkSwitchAccessPolicy` add new attribute `AccessPolicyNumber`.
## [3.0.2] - 2024-05-29
### Changed - `ResponseWirelessGetNetworkWirelessSSIDFirewallL3FirewallRulesRules` add new attribute `IpVer`. - `RequestWirelessUpdateNetworkWirelessSSIDFirewallL3FirewallRulesRules` add new attribute `IpVer`.
## [3.0.3] - 2024-06-13
### Changed - Adding request body for `UpdateOrganizationApplianceVpnThirdPartyVpnpeers` in `appliance` settings.
Develop v3.0.4
### Changed - `ResponseWirelessGetNetworkWirelessRfProfiles`is now an array.
## [3.0.5] - 2024-07-09
### Changed - Managing different types of values are accepted in `appliance_traffic_shapping` operations. - Managing different types of values are accepted in `wireless_ssids_firewall_l7FirewallRules` operations.
### Changed - Managing different types of values are accepted in `appliance_traffic_shapping` operations. - Managing different types of values are accepted in `wireless_ssids_firewall_l7FirewallRules` operations.
Develop v3.0.6
v3.0.7 new version
### Changed - update switch.go ResponseItemOrganizationsGetOrganizationDevices.Imei is now a *float64. - update wireless.go ResponseWirelessGetDeviceWirelessRadioSettingsFiveGhzSettings.ChannelWidth is now a string.
## [3.0.8] - 2024-08-05
### Changed - update wireless.go, RequestWirelessUpdateDeviceWirelessRadioSettingsFiveGhzSettings.ChannelWidth is now string.
## [3.0.9] - 2024-08-05
…ance The API returns a float, which blows up if you try to unmarshal the response into an int. This change replaces the type of PerfScore from *int to *float64.
hey @fmunozmiranda, does this PR need updating? what's the reason it was closed? thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #42