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.
I was able to get my hands on a trial of cdFMC to see what modifications were necessary to adapt fmcapi to support it.
Seems like pretty much all the same api endpoints as on prem fmc...since its just a cloud hosted on prem fmc.
The main difference is that auth is handled by CDO and proxied to the cdFMC. So no username and password, just api enabled CDO user + the JWT token that is generated for that user - which seems to remain constant unless the token is revoked in CDO.
Since this was just a trial cdFMC and CDO, I don't have any devices, but was able to at least validate that the major objects (hosts, network groups, etc.) work since all that really changed here is the auth.
#201