Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(integration): correct the instance secret and config comment

Yudhi Armyndharis9662425d7829
diff --git a/src/modules/integration/entities/plugin-instance.entity.ts b/src/modules/integration/entities/plugin-instance.entity.ts
index 2165e7598..3de2beb3e 100644
--- a/src/modules/integration/entities/plugin-instance.entity.ts
+++ b/src/modules/integration/entities/plugin-instance.entity.ts
@@ -21,7 +21,8 @@ export class PluginInstance {
@Column()
secret!: string; // host-minted ingress HMAC secret; stored plaintext, masked to '***' on API reads
// (via PluginInstanceService.maskedView + the provisioning controller's reveal flag), exposed
- // in full only on mint and regenerate-secret. Note: instance `config` is NOT secret-redacted.
+ // in full only in the create and regenerate-secret responses. Config fields flagged `secret` in
+ // the plugin's configSchema are masked by maskedView on every read, those responses included.
@Column({ type: 'varchar', nullable: true })
verifyToken!: string | null; // optional provider challenge token