Skip to content
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.

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

suggested replacement for binary_cache_secret_key_file is dysfunctional #679

Open
sbourdeauducq opened this issue Sep 18, 2019 · 4 comments

Comments

@sbourdeauducq
Copy link

I was using binary_cache_secret_key_file=some_file and, after upgrading Hydra, this stopped working with the message:

hydra.conf: binary_cache_secret_key_file is deprecated and ignored. use store_uri=...?secret-key= instead

I have replaced it with store_uri=auto?secret-key=some_file and it is still unhappy:

hydra-queue-runner: warning: unknown setting 'secret-key'

What is the proper replacement for binary_cache_secret_key_file=some_file?
Why does hydra print confusing messages here?

@edolstra
Copy link
Member

secret-key is an option of BinaryCacheStore, so it doesn't work with the local store (i.e. auto). For the local store, you have to set secret-key-files in nix.conf (not hydra.conf).

@sbourdeauducq
Copy link
Author

Okay, then what is the recommended setting for serving signed binaries from the local store via Hydra?

twhitehead added a commit to twhitehead/hydra that referenced this issue Jan 7, 2020
Using the output path to avoid repeating previously failued builds
results to changes in fixed output paths not being rebuilt (e.g.,
updating a src url). Use the derivation path instead to fix this.
twhitehead added a commit to twhitehead/hydra that referenced this issue Jan 9, 2020
Using the output path to avoid repeating previously failued builds
results to changes in fixed output paths not being rebuilt (e.g.,
updating a src url). Use the derivation path instead to fix this.
@twhitehead
Copy link
Contributor

Sorry for the noise on this ticket. I accidentally typed 679 instead of 697 in my commit message.

@kquick
Copy link
Contributor

kquick commented Jan 12, 2020

See also #548

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

No branches or pull requests

4 participants