Skip to content

feat: Simple 1Password integration#1118

Open
GooRoo wants to merge 6 commits into
Finsys:mainfrom
GooRoo:feature/onepassword
Open

feat: Simple 1Password integration#1118
GooRoo wants to merge 6 commits into
Finsys:mainfrom
GooRoo:feature/onepassword

Conversation

@GooRoo

@GooRoo GooRoo commented May 30, 2026

Copy link
Copy Markdown

Proposed change

This PR adds an integration with 1Password for homelab enthusiasts like myself. It does not support 1Password Connect Servers for business users.

Users now have an ability to add 1Password service accounts in their settings:
CleanShot 2026-05-30 at 14 42 25@2x

It's possible to bind a service account to a stack:
CleanShot 2026-05-30 at 14 44 04@2x

  1. A dropdown to select a service account.
  2. A non-secret var with an op://-reference as its value (will be replaced with a real secret upon deployment).
  3. An ID for the 1Password Environment (the whole content will be injected during deployment as secrets).
  4. The environment vars from the 1Password Environment that a container needs should (as always) be listed in the compose file.

Results

CleanShot 2026-05-30 at 14 46 31@2x
  1. The secrets injected from 1Password Environment.
  2. An interpolated op-reference.

Works with git stacks and .env files too! (Although I haven't tested it much with Hawser yet, it looks like it should work as well).

I tried to keep this feature as non-intrusive as possible.

Closes #1029.

Type of change

  • Bug fix: non-breaking change which fixes an issue.
  • New feature / Enhancement: non-breaking change which adds functionality.
  • Breaking change: fix or feature that would cause existing functionality to not work as expected.
  • Other. Please explain:

@CLAassistant

CLAassistant commented May 30, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@GooRoo

GooRoo commented Jul 4, 2026

Copy link
Copy Markdown
Author

Should I resolve the conflicts or close the PR?

@craiglemon

Copy link
Copy Markdown

Should I resolve the conflicts or close the PR?

I am interested in this feature, and keen to see it merged into main branch 👍

GooRoo added 6 commits July 11, 2026 22:43
# Conflicts:
#	src/lib/server/stacks.ts

# Conflicts:
#	drizzle-pg/meta/_journal.json
#	drizzle/meta/0007_snapshot.json
#	drizzle/meta/_journal.json
#	src/lib/server/db/drizzle.ts
#	src/lib/stores/auth.ts
#	src/routes/settings/+page.svelte
…but only when a 1Password service account is bound to a stack.
@GooRoo
GooRoo force-pushed the feature/onepassword branch from aef4735 to c11b0d0 Compare July 11, 2026 22:07
@GooRoo

GooRoo commented Jul 11, 2026

Copy link
Copy Markdown
Author

Rebased onto the current main.

@GooRoo

GooRoo commented Jul 16, 2026

Copy link
Copy Markdown
Author

Hey @jotka, is there any chance to get this merged? Are there any obstacles I can address?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] 1Password support

3 participants