Fmcapi

Latest version: v20240503.0

Safety actively analyzes 630052 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

20191017.0

Bug fixes
Improved debug outputs
Added ability to add source_sgt into AccessRules but it appears the FMC isn't using it yet.
Added access to defaultAction in AccessRules.
Added access to IKESettings API
Added access to IPsecSettings API
Added access to AdvancedSettings API
Added access to Endpoints API
Expanded the Example to include an example of separation of user data and code.
Added extendedACL support to EndPoints.
Modified INFO logging. Move some messages into DEBUG/ERROR/WARNING levels instead.

20191002.0

There was a "bug" that caused fmcapi AccessRules to not put/post to FMC. Fixed.
Alpha (untested) ability to add source_sgt to AccessRules.

20190923.0

I don't think there were any new features. This release is more about improving the code quality.

20190915.1

This release has a drastic reorganization of the api_objects package into sub-packages that align with the Cisco FMC API Quick Start Guide organization of the API methods.
This meant that some of the "old" names of some of the fmcapi classes needed to be changed. The old name will work for a while but you should get a deprecation warning if you use the old name. When the removal of the old names happens has yet to be determined... 2021'ish?
Improvements to the token refresh/generation in this release too.

20190911.0

Added a "dry_run" feature. This will allow you to see what would have been sent to the FMC's API. Works for GET, POST, PUT. (I forgot to add it to DELETE. I'll fix that in the next release.)

Fixed "enabled" always being False in PhysicalInterface Class.

Adjusted, again, the token refresh logic.

20190910.1

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.