awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-09 01:28:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: docs for ID and slug support across all operator CRDS

Browse Source
This commit is contained in:
Daniel Hougaard
2025-09-05 14:15:27 +02:00
parent b53c250ded
commit e9c14d0c0f
3 changed files with 50 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/platforms/kubernetes/infisical-push-secret-crd.mdx
+14 -1
View File
@@ -44,7 +44,8 @@ Before applying the InfisicalPushSecret CRD, you need to create a Kubernetes sec
deletionPolicy: Delete # If set to delete, the secret(s) inside Infisical managed by the operator, will be deleted if the InfisicalPushSecret CRD is deleted.
destination:
projectId: <project-id>
projectId: <project-id> # Either projectId or projectSlug is required
projectSlug: <project-slug>
environmentSlug: <env-slug>
secretsPath: <secret-path>
@@ -203,6 +204,18 @@ After applying the InfisicalPushSecret CRD, you should notice that the secrets y
<Accordion title="destination.projectId">
The project ID where you want to create the secrets in Infisical.
<Note>
Please note that you can only use either `projectId` or `projectSlug` in the `destination` field.
</Note>
</Accordion>
<Accordion title="destination.projectSlug">
The project slug where you want to create the secrets in Infisical.
<Note>
Please note that you can only use either `projectId` or `projectSlug` in the `destination` field.
</Note>
</Accordion>
<Accordion title="destination.environmentSlug">