Retry mechanism for pubsub

[JaydipGabani]

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Audit prevents publishing a violation if it fails on the first try. It would be helpful to have some sort of retry mechanism to make sure we do not move on after just one publishing try in the event of an error.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The following questions might help in understanding some of the requirement:

• Can we rely on retry logic on the underlying pub sub tool?
• Should the driver implement this logic of retry?
• How to make the retries configurable? (pass it in connection client config?)

Environment:

• Gatekeeper version:
• Kubernetes version: (use kubectl version):

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[maxsmythe]

Are we still working on pubsub?

[JaydipGabani]

Not working actively on this issue, but we can keep it open and see if ppl want this or not maybe?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[JaydipGabani]

Keep this open

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.