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

dotnet user-secrets edit #46919

Open
dotnet-policy-bot opened this issue Mar 7, 2024 · 4 comments
Open

dotnet user-secrets edit #46919

dotnet-policy-bot opened this issue Mar 7, 2024 · 4 comments

Comments

@dotnet-policy-bot
Copy link
Member

dotnet-policy-bot commented Mar 7, 2024

Is your feature request related to a problem? Please describe.

Editing user secrets via dotnet user-secret isn't the most comfortable way. In many cases, I want to edit the underlying JSON file. In VS one can do that by right clicking the project and selecting Edit User Secrets. Having a way to do this from the CLI would be nice.

Describe the solution you'd like

Git has a similar issue in their config system and it exposes a git config --edit command that launches the configuration file in the default editor.

I know one can get the path via dotnet user-secrets list -v but that isn't as obvious as a top-level command like dotnet user-secret edit.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Request triage from a team member label Mar 7, 2024
@terrajobst
Copy link
Contributor

Sorry, didn't mean to use the @dotnet-policy-bot account to file this issue. Was still logged in as it :-/

@MiYanni MiYanni transferred this issue from dotnet/sdk Feb 14, 2025
@MiYanni
Copy link
Member

MiYanni commented Feb 14, 2025

Seems dotnet user-secret comes from Microsoft.Extensions.Configuration.UserSecrets, which is created in the runtime repo. So, I've transferred the issue here.

Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-extensions-configuration
See info in area-owners.md if you want to be subscribed.

@tarekgh
Copy link
Member

tarekgh commented Feb 18, 2025

@MiYanni the issue here is not complaining about the wrong result coming from the library Microsoft.Extensions.Configuration.UserSecrets but asking for easier way to edit the user secrets in the CLI In VS one can do that by right clicking the project and selecting Edit User Secrets. Having a way to do this from the CLI would be nice..

I moved the issue back to SDK repo. You can move it to any other repo if SDK is not the right one for CLI. Thanks!

@tarekgh tarekgh transferred this issue from dotnet/runtime Feb 18, 2025
@MiYanni MiYanni removed untriaged Request triage from a team member type-investigation labels Mar 6, 2025
@MiYanni MiYanni removed their assignment Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants