Reading updated secret values in triggered function

MongoDB Atlas Atlas Triggers & Functions
1

I have a scheduled function that is using the Mongo API to update a secret value, which works as expected. Another scheduled function does not see the new value and instead gets the old value until the function is redeployed.

Is this expected behavior? Are there other options to rotate a secret value that can be read by a scheduled function?

1 Like
2

Hi Brad,

I understand this is an old thread however I was not able to reproduce the problem.

Steps I took:

  • Create a secret value with incorrect secret
  • Enable scheduled trigger which accesses the secret value via context.values.get()
  • Wait for trigger to run and result in error
  • Update the secret using the admin api PUT request to the correct secret
  • Wait for the next instance of the trigger to run
  • Notice that there is no error because the secret was corrected

This was done while drafting was enabled in the app.

If anyone else runs into any problem with updating the secret via admin API, please provide details.

Regards
Manny