How does the k8s operator restart deployments?
I don't see in the documentation anywhere but I'd like to know how the operator restarts deployments. My main concern is that if a secret is updated, a deployment will hard-restart and possibly interrupt an operation mid-request. Is there a way to configure how it restarts deployments, with a custom shutdown command that can be handled by the service properly, finish it's current request and then restart nicley?Connect Server PATCH /title is deleting fields from Item
Running into a weird one with a connect api / server spun up in AWS. When I attempt to update the title of a vault item, any "extra" fields, sections, or files are dropped. Here's a psuedocode example. Item { "category": "DOCUMENT", "fields": [{ "id": "notesPlain", ... }], "files": [{ "content_path": "/v1/vaults/111/items/222/files/333/content", "id": "333", "name": "filename.pdf", "size": 369343 }, { "content_path": "/v1/vaults/111/items/222/files/444/content", "id": "444", "name": "filename.jpeg", "section": { "id": "add more" } }], "id": "222", "sections": [{ "id": "add more" }], "title": "Test Item" "vault": { "id": "111", "name": "Test Vault" } } Request PATCH {domain}/v1/vaults/111/items/222 -d [{ "op": "replace", "path": "/title", "value": "Test Item v2" }] Resulting Item { "category": "DOCUMENT", "fields": [{ "id": "notesPlain", ... }], "files": [{ "content_path": "/v1/vaults/111/items/222/files/333/content", "id": "333", "name": "filename.pdf", "size": 369343 }], "id": "222", "title": "Test Item v2" "vault": { "id": "111", "name": "Test Vault" } } Both the second file and section are removed. From the /activity endpoint it appears that a single "UPDATE" was done on the item, so I don't think it's the connect server "duplicating" or sending secondary destructive requests or anything. I've also tried PUT and sent the entire original payload, only modifying the title, but this also removes the fields. Is there a way that we can programmatically update the title without dropping data out of the item?
IntelliJ IDEA Git plugin not authenticating
When I attempt to push from IntelliJ (via the Git plugin), the 1Password authentication prompt doesn't appear, and eventually the push fails with: sign_and_send_pubkey: signing failed for ED25519 "SSH Key" from agent: communication with agent failed git@github.com: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. When I open a terminal and authenticate IntelliJ manually, only then can I actually push anything. According to the 1Password ssh-agent docs, IntelliJ should work, but it's not. OS: NixOS 24.11 IntelliJ version: IntelliJ IDEA 2024.3.2.2 (Ultimate Edition) Build #IU-243.23654.189 1Password version: 8.10.48 op version: 2.30.2 Command IntelliJ git plugin runs for pushing (I figured it might be useful because IntelliJ adds some options to it): git -c credential.helper= -c core.quotepath=false -c log.showSignature=false push --progress --porcelain origin refs/heads/main:main
Cannot connect connect-server to 1password from k8s
Hello. I have a problem with running 1Password operator in k8s cluster. Onepassword-connector does not connect to the server at all. First I had problems with onepassword-credentials.json being fetched by the connector-api and connector-sync containers if they were declared as: env: - name: OP_SESSION valueFrom: secretKeyRef: name: op-credentials key: 1password-credentials.json So I passed them via volumes / volumeMounts and defined the variable like this: volumes: - name: credentials secret: secretName: op-credentials (...) env: - name: OP_SESSION value: /home/opuser/.config/1password-credentials.json volumeMounts: - mountPath: /home/opuser/.config name: credentials readOnly: true Here I put my code to make it clear how I create the deployment: Gitlab Unfortunately I still can't connect to the server, and on the page: https://my.1password.com/developer-tools/infrastructure-secrets/connect/{connect_id} There is no information about the connection of my connect server, it only says "Not yet deployed" Neither the connect-api container nor the connect-sync inside the onepassword-connect pod log any errors. Only errors I have are for operator and OnePasswordItem, which is: 2025-02-17T20:31:08Z ERROR Reconciler error {"controller": "onepassworditem", "controllerGroup": "onepassword.com", "controllerKind": "OnePasswordItem", "OnePasswordItem": {"name":"example","namespace":"onepassword"}, "namespace": "onepassword", "name": "example", "reconcileID": "a1ba0a9c-7388-454e-9ce6-074cb6621e5c", "error": "Failed to retrieve item: Get \"http://onepassword-connect:8080/v1/vaults?filter=title+eq+%22Development%22\": net/http: invalid header field value for \"Authorization\""} sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler /workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:329 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem /workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:266 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 /workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:227 Could I ask for help in finding the problem? MarPi82
Trouble getting document items in Kubernetes with 1P Connect Operator
Hey everyone, I'm trying to get a document out of 1P and into a k8s secret with the Connect Operator, version 1.8.1. I can get Login items but not Document items, even though there seems to be a discussion about this exact topic stating that Documents are supported as of version 1.3.0. Does anyone else have experience with this? --- apiVersion: onepassword.com/v1 kind: OnePasswordItem metadata: name: config-file-dot-yaml namespace: default spec: itemPath: "vaults/dev/items/config-file.yaml" This is the OnePasswordItem I have. The Document config-file.yaml is in the vault dev, and kubectl describe secret config-file-dot-yaml returns an event of "No items found with identifier 'config-file.yaml' " Is there any examples out there of getting the document? Thanks!Rails integration
Hi, I've been reading today about how you can integrate 1Password with Rails Kamal. Can I integrate 1Password with the regular Rails Credentials file? If so, is there any documentation for this? 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser: Not ProvidedCan't connect to 1password from Raycast
If I don't have the 1password app open at the same time, the Raycast extension doesn't want to connect an authenticate. It either keeps on trying to Authenticate forever, or it tells me to update the app (which I have), or it tell me something about context window exceded. The cli is also up to date.
Welcome to the SDKs User Group!
Hello SDKs Community, Welcome to the 1Password SDKs User Group—your new hub for all things development, security, and creativity! Whether you're a coding wizard weaving 1Password into your apps or a curious explorer just dipping your toes into the SDKs waters, you’ve found your tribe. What this group is for: Collaborate and learn: Connect with other developers to share tips, code snippets, and best practices for leveraging the 1Password SDKs in your projects. Expand your expertise: Grow your knowledge of the 1Password SDKs to build secure, seamless, and user-friendly integrations. Stay informed: Get updates on the latest SDKs features, documentation, and resources directly from the 1Password team. Reminders: Security first: Please avoid sharing sensitive information, such as API keys or credentials, in this group. Our priority is keeping your data and integrations secure. Technical support: For troubleshooting or technical assistance, visit support.1password.com. Feedback and ideas: Have suggestions for improving the SDKs or want to share your experience? Post in the discussion forum or tag me directly! This group is all about you—your ideas, your questions, and your wins. So don’t be shy! Introduce yourself, share what you’re working on, or ask that question. Let’s make this space a powerhouse of innovation and collaboration. Can’t wait to see what you’ll build!
