Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

dotnet user-secrets {command} --project {path} does not support relative paths #77

Closed
dougbu opened this issue May 12, 2016 · 1 comment
Labels

Comments

@dougbu
Copy link
Member

dougbu commented May 12, 2016

  1. It isn't clear why we need the --project option at all. The dotnet user-secrets command must be executed in a project directory with Microsoft.Extensions.SecretManager.Tools fully configured.
  2. If this option is needed, it should support relative paths. That would at least be useful in corner cases where user secrets are used in a group of projects but only one has the tool configured.
  3. dotnet user-secrets list --project $pwd/../../src/UserSecrets.work is ugly as sin.
  4. What is the parameter named root?

For example

dotnet user-secrets list --project ../../src/UserSecrets.work

Results in

critical: Command failed : The path must be absolute.
Parameter name: root
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants