Ability to mount `1password-credentials.json` via PVC

[yalattas]

Summary

All examples refers to credentials: variable to provide content of 1password-credentials.json file. Yet, some are using GitOps to render the template and the then apply without using helm release.

Another people, will use helm CICD, will be a bit difficult to pass extra argument other than what's expected (values.yaml and secrets.yaml )

Another case where people are using helmfile instead,

Therefore, its better to allow volume mounting into operator container so I can put the content of the file in secrets then mount the secret into a specific path in operator container and point the application to use this JSON file

dataVolume:
    # The name of the shared volume used between 1Password Connect Containers
    name: shared-data
    # The type of the shared volume used between
    # 1Password Connect Containers
    type: emptyDir
    # Desribes the fields and values for configuration of
    # shared volume for 1Password Connect
    values: {}

Above snippet isn't clear and haven't found sufficient example of its usage. Values expects dictionary, key=value how can I provide JSON content to be shared across pods

Use cases

1- fetch JSON from external secret within k8s cluster
2- fetch JSON from external ConfigMap within k8s cluster

Proposed solution

Allow mounting to operator pod via helm chart

Is there a workaround to accomplish this today?

Currently base64, yet initially failed for some reason, when I followed the example, encoding values was different.
I am using GitOps so CD solution will do the apply and will be responsible to generate the secret in advance for 1password operator to use it

[speedythesnail]

Almost a year later, what I did is:

Created the below manifest in the namespace I deployed the operator to:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: 1password-pvc
  namespace: credentials
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 1Gi

under the connect section of the values for the helm chart:

  # 1Password Connect volume shared between 1Password Connect Containers
  dataVolume:
    # The name of the shared volume used between 1Password Connect Containers
    name: 1password-pvc
  type: persistentVolumeClaim
  values:
    claimName: 1password-pvc

I would contribute a PR, but I'm done wasting my time trying to contribute to open source projects, only for my PR to wait for a review for 2 months, before someone asks for a slight change (usually a nitpick), then I make the change and the request is never approved.

Looking at this repo, the last pull request was closed in December of last year, so you're probably better off just forking the helm chart to make any changes you'd like.

[jamescallumyoung]

See also #98 for another solution when working with GitOps.