Found an solution myself, in general I cannot understand why official packages do not support functions v2 when v1 is already deprectated...

According to the firebase-functions implementation:

export class SecretParam {
  static type: ParamValueType = "secret";
  name: string;

  constructor(name: string) {
    this.name = name;
  }

  /** @internal */
  runtimeValue(): string {
    const val = process.env[this.name];
    if (val === undefined) {
      logger.warn(
        `No value found for secret parameter "${this.name}". A function can only access a secret if you include the secret in the function's dependency array.`
      );
    }
    return val || "";
  }

  /** @internal */
  toSpec(): ParamSpec<string> {
    return {
      type: "secret",
      name: this.name,
    };
  }

  /** Returns the secret's value at runtime. Throws an error if accessed during deployment. */
  value(): string {
    if (process.env.FUNCTIONS_CONTROL_API === "true") {
      throw new Error(
        `Cannot access the value of secret "${this.name}" during function deployment. Secret values are only available at runtime.`
      );
    }
    return this.runtimeValue();
  }
}

So just writing the variabled/secrets in process.env gets the job done:

const secretsFile = readFileSync('functions/.secret.local', {
  encoding: 'utf-8',
});
const envFile = readFileSync('functions/.env.local', {
  encoding: 'utf-8',
});
const secrets = secretsFile.split('\n').filter((line) => line.length);
const envVariables = envFile.split('\n').filter((line) => line.length);

for (const line of [...secrets, ...envVariables]) {
  const [key, value] = line.split('=');

  process.env[key] = value;
}

Secret Manager Values in offline testing #255

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions