This is built on the API I know, but I’m having some issues and hoping to get perspective from someone who is directly responsible for this module.
My use case:
Each night I load all certificate objects along with some details into a reporting db that we in turn use for reporting. It’s much more flexible for us to work with the data outside of the Venafi UI to produce the reports we need.
I use find-venaficertificate to get the initial list of certificate objects
Then I use get-venaficertificate to get additional details
This is a relatively slow process – the initial find-venaficertificate takes about 15 minutes to return a list of all certificates, then churning through that list running get-venaficertificate takes about 2.5-3 hours running 10 threads at the same time.
Part of the slowness is due in part to the Venafi TPP server getting hung up periodically
In addition to this, and the primary reason for this email, we recently needed to add some additional attributes which are not included in the data described above
Here I’m using Get-TppAttribute supplying the path to the certificate object and retrieving 5 attributes which are standard (non-custom)
This process of getting this data across 150k certs takes approximately 5 hours looping through
Then recently I started getting an error from within the venafips module itself that causes the loop to error out
So then, I’ve upgraded the venafips module to the latest 6.3 and now the performance seems to have gotten worse.
Now the get-TPPAttribute\Get-VdcAttribute shows a progress bar for every request and it’s taking about 5 seconds per request
This is built on the API I know, but I’m having some issues and hoping to get perspective from someone who is directly responsible for this module.
My use case:
Each night I load all certificate objects along with some details into a reporting db that we in turn use for reporting. It’s much more flexible for us to work with the data outside of the Venafi UI to produce the reports we need.
In addition to this, and the primary reason for this email, we recently needed to add some additional attributes which are not included in the data described above