Hey team! Just found a bug in the secret imports feature. The documentation states that when importing 2 folders with the same secret key, the second import (bottom) takes precedence.

If two secret imports contain secrets with the same name, then the secret value from the bottom-most secret import is taken

. However, when we used this in our app, we found that sometime in the last few weeks, this broke and now the first one (top one) takes precedence. After changing this, it worked. Is this an intentional change where documentation wasn't updated? Or is the documentation correct but the feature is broken?

Hi @Gateek Chandak, how are you reading the secrets from the API? are you using one of our SDK's, the operator, CLI, or something else?

We use the Infisical Kubernetes Operator with Machine Identity (Universal Auth)

Thank you Gateek. What you are referring to is actually supported in the v4 secrets endpoints. The operator is currently on the v3 secrets endpoints, but we're currently in the midst of rolling out an update to the operator which will include better structured CRD's, and the inclusion of the v4 secrets router!

When that happens, will the order of precedence go back to being bottom up?

@Gateek Chandak, we're taking a look at this on our side to see if behavior has shifted. We'll let you know as soon as we have an update for you!