Currently, through my tests, the reading of credentials via the secret is a one time thing. That means if you rotate out the credentials you have to delete the trigger and re-create it.
Much like PODs do when consuming secrets and/or configmaps, the trigger should see updates and update the credentials used.
FEATURE REQUEST?:
Currently, through my tests, the reading of credentials via the secret is a one time thing. That means if you rotate out the credentials you have to delete the trigger and re-create it.
Much like PODs do when consuming secrets and/or configmaps, the trigger should see updates and update the credentials used.