Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure App Config Label patch #2921

Merged
merged 2 commits into from
Dec 27, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
add docs for label and refereces
maidul98 committed Dec 26, 2024

Unverified

The committer email address is not verified.
commit 05139820a5d35ff113be9e09d3a28da34aaa8076
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
21 changes: 21 additions & 0 deletions docs/integrations/cloud/azure-app-configuration.mdx
Original file line number Diff line number Diff line change
@@ -30,6 +30,27 @@ description: "How to sync secrets from Infisical to Azure App Configuration"

Press create integration to start syncing secrets to Azure App Configuration.
</Step>
<Step title="Additional Configuration">

#### Azure references
When adding secrets in Infisical that reference Azure Key Vault secrets, Infisical will automatically sets the content type to `application/vnd.microsoft.appconfig.keyvaultref+json;charset=utf-8` in Azure App Configuration.
The following reference formats are automatically detected when added on Infisical's side:
- `{ "uri": "https://my-key-vault.vault.azure.net/secrets/my-secret" }`
- `https://my-key-vault.vault.azure.net/secrets/my-secret`

### Azure Labels
You can sync secrets from Infisical to Azure with custom labels by enabling the `Use Labels` option during setup:

**When enabled**: Secrets will be pushed to Azure with your specified label

**When disabled**: Secrets will be pushed with an empty (null) label

<Info>
If you have set the initial sync to `import` have behavior, the label selection affects which secrets are imported from Azure:
- With `Use Labels` disabled: Only secrets with empty labels are imported on initial sync
- With `Use Labels` enabled: Only secrets matching your specified label are imported on initial sync
</Info>
</Step>
</Steps>

</Tab>

Unchanged files with check annotations Beta

});
if (!process.env.AUDIT_LOGS_DB_CONNECTION_URI && !process.env.AUDIT_LOGS_DB_HOST) {
console.info("Dedicated audit log database not found. No further migrations necessary");

Check warning on line 17 in backend/src/db/auditlog-knexfile.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
process.exit(0);
}
console.info("Executing migration on audit log database...");

Check warning on line 21 in backend/src/db/auditlog-knexfile.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
export default {
development: {
};
const up = async (knex: Knex): Promise<void> => {
console.info("Dropping primary key of audit log table...");

Check warning on line 27 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
await knex.schema.alterTable(TableName.AuditLog, (t) => {
// remove existing keys
t.dropPrimary();
`
);
console.log(

Check warning on line 42 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
"Deleting existing audit log indices:",
indexNames.rows.map((e) => e.indexname)
);
}
// renaming audit log to intermediate table
console.log("Renaming audit log table to the intermediate name");

Check warning on line 52 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
await knex.schema.renameTable(TableName.AuditLog, INTERMEDIATE_AUDIT_LOG_TABLE);
if (!(await knex.schema.hasTable(TableName.AuditLog))) {
})
.toString();
console.info("Creating partition table...");

Check warning on line 75 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
await knex.schema.raw(`
${createTableSql} PARTITION BY RANGE ("createdAt");
`);
console.log("Adding indices...");

Check warning on line 80 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
await knex.schema.alterTable(TableName.AuditLog, (t) => {
t.index(["projectId", "createdAt"]);
t.index(["orgId", "createdAt"]);
t.index("projectId");
});
console.log("Adding GIN indices...");

Check warning on line 89 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
await knex.raw(
`CREATE INDEX IF NOT EXISTS "audit_logs_actorMetadata_idx" ON ${TableName.AuditLog} USING gin("actorMetadata" jsonb_path_ops)`
);
console.log("GIN index for actorMetadata done");

Check warning on line 94 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
await knex.raw(
`CREATE INDEX IF NOT EXISTS "audit_logs_eventMetadata_idx" ON ${TableName.AuditLog} USING gin("eventMetadata" jsonb_path_ops)`
);
console.log("GIN index for eventMetadata done");

Check warning on line 99 in backend/src/db/manual-migrations/partition-audit-logs.ts

GitHub Actions / Check TS and Lint

Unexpected console statement
// create default partition
console.log("Creating default partition...");