Closed abelikt closed 1 year ago
This issue is still valid.
configure_bridge.sh
creates a device certificate on every run and upload it to our Cumulocity tenant.If this is just for the CI/CD runner, then we could use my open source tool go-c8y-cli
After setting the required environment variables for the url, username, password etc, deleting all of the certificates can be done using:
c8y devicemanagement certificates list --includeAll | c8y devicemanagement certificates delete
If this is just for the CI/CD runner, then we could use my open source tool go-c8y-cli
After setting the required environment variables for the url, username, password etc, deleting all of the certificates can be done using:
c8y devicemanagement certificates list --includeAll | c8y devicemanagement certificates delete
After I saw your demo, I came back to this issue as I really think this is the solution :) It is just for the CI/CD runner.
Is this still relevant? I don't think so.
The new integration test setup does an automatic cleanup of any uploaded device certificates to Cumulocity IoT.
Is your feature request related to a problem? Please describe.
Every once in a while we should delete uploaded certificates from C8y.
Describe the solution you'd like
Have a small script in the QA repo that does the job with the c8y_api. Unsure if we should just delete all certificates or avoid some that are in use.
Describe alternatives you've considered
It was mentioned that even millions of certificates shouldn't matter. So the alternative is to do nothing :)
Additional context
context