Skip to content

Push each package once and document limitations #1

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
jacalapa merged 1 commit into from
Oct 12, 2026
Merged

Push each package once and document limitations #1

Show file tree
Hide file tree
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
18 changes: 1 addition & 17 deletions .github/workflows/publish-nuget.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,23 +79,7 @@ jobs:

- name: Push to NuGet
run: |
dotnet nuget push ./nupkgs/Kododo.ConfigWay.Core.*.nupkg \
--api-key ${{ secrets.NUGET_API_KEY }} \
--source https://api.nuget.org/v3/index.json \
--skip-duplicate
dotnet nuget push ./nupkgs/Kododo.ConfigWay.*.nupkg \
--api-key ${{ secrets.NUGET_API_KEY }} \
--source https://api.nuget.org/v3/index.json \
--skip-duplicate
dotnet nuget push ./nupkgs/Kododo.ConfigWay.UI.*.nupkg \
--api-key ${{ secrets.NUGET_API_KEY }} \
--source https://api.nuget.org/v3/index.json \
--skip-duplicate
dotnet nuget push ./nupkgs/Kododo.ConfigWay.PostgreSQL.*.nupkg \
--api-key ${{ secrets.NUGET_API_KEY }} \
--source https://api.nuget.org/v3/index.json \
--skip-duplicate
dotnet nuget push ./nupkgs/Kododo.ConfigWay.SqlServer.*.nupkg \
dotnet nuget push ./nupkgs/*.nupkg \
--api-key ${{ secrets.NUGET_API_KEY }} \
--source https://api.nuget.org/v3/index.json \
--skip-duplicate
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,7 @@ Sensitive fields behave as follows:
- The real value is never returned by the API. When a value is stored, the API returns `"***"`. When nothing is stored, it returns `null`.
- Submitting an empty value is treated as "no change". To remove a stored sensitive value, use the reset button.
- The reset button appears when a sensitive value is stored. Resetting deletes the stored value and lets the underlying configuration layer (appsettings.json, environment variable) take effect again without a restart.
- Sensitive values are masked in the UI and the API only. The store keeps them as plain text, so restrict access to the database accordingly.

## Customizing UI labels and descriptions

Expand Down Expand Up @@ -204,6 +205,11 @@ app.UseConfigWay()

> Use `IOptionsSnapshot<T>` or `IOptionsMonitor<T>` in your code to always get the latest values after a reload.

## Limitations

- Changes are reloaded only in the instance that saved them. When the app runs as several replicas, the other replicas pick up the new values after a restart.
- Saves do not check for concurrent edits. If two people edit the same section at the same time, the last save wins.

## Custom store

You can replace the built-in in-memory store with any backend by implementing `IStore` from `Kododo.ConfigWay.Core`:
Expand Down
Loading