Skip to content

Commit

Permalink
chore:Update docs/Configuration.md with info about appsettings.json (#…
Browse files Browse the repository at this point in the history
…1098)

Also remove iadvertently added appssetings.DevelopmentAuth.json
  • Loading branch information
elsand authored Sep 9, 2024
1 parent 9e2b27c commit 9775127
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 15 deletions.
5 changes: 4 additions & 1 deletion docs/Configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,9 @@ When a pull request containing configuration changes is merged with main, one of

Each runtime / presentation layer adds its own configuration keys to azure app configuration through `appsettings.json` and `appsettings.[Environment].json` with a runtime tag, indicating which runtime that owns that specific configuration value.

## 2.4 Local-only configuration
When developing, it is often useful to have configuration that is only used locally, eg. to override default `LocalDevelopment` configuration values. If a `appsettings.local.json` file is present, this file will take precedence over all other configuration files after merge. This file should **not** be checked in to the repository (it is in `.gitignore`).

# 3. Autogenerated secrets
Autogenerated secrets are secrets that is generated and used by the IaC when creating resources in Azure. When a resource which require a password is generated, the IaC bootstrap script will create a new key value pair with the name of the password as its key, and the actual password as its value. The IaC then checks if the environments key vault has a secret with the same name. If it does, the autogenerated password will be discarded and the "cached" password will be used. If not, it will add/"cache" the autogenerated password to the key vault and use it when creating the resource.

Expand Down Expand Up @@ -107,4 +110,4 @@ There are two conventions, one that targets a specific environment, and one "any
| iDoNotFollowTheConvention | | false | Is ignored as it does not follow any convention. |

## 4.2. How to
Instruct your friendly secrets manager to modify the desired key value pair in the source key vault before merging your pull request to the main branch.
Instruct your friendly secrets manager to modify the desired key value pair in the source key vault before merging your pull request to the main branch.

This file was deleted.

0 comments on commit 9775127

Please sign in to comment.