To be able to move the repository on the new organization and to facilitate external developer integration we need to create a standalone dev stack and use external secret.
35 lines
1.2 KiB
YAML
35 lines
1.2 KiB
YAML
apiVersion: external-secrets.io/v1beta1
|
|
kind: ClusterSecretStore
|
|
metadata:
|
|
name: bitwarden-login-{{ $.Release.Namespace }}
|
|
namespace: external-secrets
|
|
spec:
|
|
provider:
|
|
webhook:
|
|
url: "http://bitwarden-cli-{{ $.Release.Namespace }}.{{ $.Release.Namespace }}.svc.cluster.local:8087/object/item/{{`{{ .remoteRef.key }}`}}"
|
|
headers:
|
|
Content-Type: application/json
|
|
result:
|
|
jsonPath: "$.data.login.{{`{{ .remoteRef.property }}`}}"
|
|
---
|
|
apiVersion: external-secrets.io/v1beta1
|
|
kind: ClusterSecretStore
|
|
metadata:
|
|
name: bitwarden-fields-{{ $.Release.Namespace }}
|
|
spec:
|
|
provider:
|
|
webhook:
|
|
url: "http://bitwarden-cli-{{ $.Release.Namespace }}.{{ $.Release.Namespace }}.svc.cluster.local:8087/object/item/{{`{{ .remoteRef.key }}`}}"
|
|
result:
|
|
jsonPath: "$.data.fields[?@.name==\"{{`{{ .remoteRef.property }}`}}\"].value"
|
|
---
|
|
apiVersion: external-secrets.io/v1beta1
|
|
kind: ClusterSecretStore
|
|
metadata:
|
|
name: bitwarden-attachments-{{ $.Release.Namespace }}
|
|
spec:
|
|
provider:
|
|
webhook:
|
|
url: "http://bitwarden-cli-{{ $.Release.Namespace }}.{{ $.Release.Namespace }}.svc.cluster.local:8087/object/attachment/{{`{{ .remoteRef.property }}`}}?itemid={{`{{ .remoteRef.key }}`}}"
|
|
result: {}
|