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
Rename default appsettings.json file to local.settings.json #122
Comments
I got the warning so i renamed appsettings.json to local.settings.json. This worked fine. Then i tried connecting to azure using the "func azure login" commands and "func azure functionapp fetch" which created a new appsettings.json instead of updating local.settings.json. I manually copied into local.settings.json. but it seems that the cli commands still expect appsettings.json. has this been fixed just not released? |
@Nitro52 It was supposed to be released with the fix you mentioned, but it looks like we missed a code path. Thanks for the bug report! Reopening issue. |
I can't repro this. |
@Nitro52 Same here, it all works correctly on Beta96. Closing issue, let us know if you have an updated repro. |
Sorry guys, i did a npm i -g azure-functions-core-tools a day or two a go, at least i thought i did. seems like i was on 94 not 96. Updated and it looks fine. |
@Nitro52 thanks for confirming |
We've gotten feedback from customers that the name
appsettings.json
is confusing. I did a poll on the Advisors group. We got 50+ responses, with most voting for the namelocal.settings.json
.We should do the following:
The text was updated successfully, but these errors were encountered: