Hi all! My team and I noticed that secret overrides do not get imported when using secret imports. Is this intentional or is there a fix/workaround for this. Essentially we are using overrides for each team member's database branch and are unable to use imports to do so.

Hi @Gateek Chandak, this is currently expected behavior - we'll work on communicating this via the UI/Docs

hey @Scott (Infisical), could I ask why? If so, is there an alternative for this, we would like to have an override for a DB variable but we cant use our imported folder.

Hey Gateek, this is primarily due resolving multiple overrides in import chains - we're exploring how and if we'd want to approach this. In the interim, for development, you could create a designated folder or env that imports the full development picture, and then add a local

DB_VARIABLE

that users can override, this way all other values are derived from the import but the local variable is overridden individually by users

If I were to add the same variable name as one of the imports, would it take precedence over the imports? I assume so based on what ive read

Yes! local values always take precedence over imported values

awesome, thank you!