Skip to content

Handle issue where DB secret already exists by requeueing and restarting the flow #506

Handle issue where DB secret already exists by requeueing and restarting the flow

Handle issue where DB secret already exists by requeueing and restarting the flow #506

Triggered via issue September 15, 2024 15:19
Status Success
Total duration 13s
Artifacts

cla.yaml

on: issue_comment
CLAssistant  /  CLAssistant
5s
CLAssistant / CLAssistant
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
CLAssistant / CLAssistant
The following actions uses node12 which is deprecated and will be forced to run on node16: otterize/cla-bot@v2.2.1-otterize. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
CLAssistant / CLAssistant
The following actions use a deprecated Node.js version and will be forced to run on node20: otterize/cla-bot@v2.2.1-otterize. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/