Skip to content

chore(doppler): declare the dotfiles/prd repo config #2837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shunkakinoki merged 1 commit into from
Sep 19, 2026
+3 −0
Merged

chore(doppler): declare the dotfiles/prd repo config #2837

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .doppler.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
setup:
- project: dotfiles

@cubic-dev-ai cubic-dev-ai Bot Sep 19, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: As committed, this file does not make Doppler resolve dotfiles/prd from the checkout, and it duplicates the flags that are still hardcoded in the Makefile. Doppler's docs are explicit that ordinary commands (secrets download, run) never read a repo-local doppler.yaml — project/config resolution goes through ~/.doppler/.doppler.yaml, which is only populated by running doppler setup. Nothing in this repo invokes doppler setup (home-manager only installs the CLI binary), and doppler-sync/doppler-diff/doppler-upload (Makefile lines 1607, 1612, 1617) still pass --project dotfiles --config prd. So the file can't help a fresh host until doppler setup --no-interactive runs, and its declared values can silently drift from the flags, which remain the only effective source of truth. Recommend wiring doppler setup --no-interactive into the bootstrap/preflight step and then removing the now-redundant --project/--config flags from the three recipes so this file is the single source of truth.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At .doppler.yaml, line 2:

<comment>As committed, this file does not make Doppler resolve `dotfiles/prd` from the checkout, and it duplicates the flags that are still hardcoded in the Makefile. Doppler's docs are explicit that ordinary commands (`secrets download`, `run`) never read a repo-local `doppler.yaml` — project/config resolution goes through `~/.doppler/.doppler.yaml`, which is only populated by running `doppler setup`. Nothing in this repo invokes `doppler setup` (home-manager only installs the CLI binary), and `doppler-sync`/`doppler-diff`/`doppler-upload` (Makefile lines 1607, 1612, 1617) still pass `--project dotfiles --config prd`. So the file can't help a fresh host until `doppler setup --no-interactive` runs, and its declared values can silently drift from the flags, which remain the only effective source of truth. Recommend wiring `doppler setup --no-interactive` into the bootstrap/preflight step and then removing the now-redundant `--project`/`--config` flags from the three recipes so this file is the single source of truth.</comment>

<file context>
@@ -0,0 +1,3 @@
+setup:
+  - project: dotfiles
+    config: prd
</file context>

config: prd
Loading