You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.funcignore is expected to behave like a .gitignore file, only preventing files from being published to an Azure Function, rather than preventing them from being committed.
For example, with a project structure such as this:
After using VSCode to deploy the function, in the Code & Test window we see MyFunctionApp\ExampleFunction1\confidential.secret exists in the app's directory.
.funcignore
is expected to behave like a.gitignore
file, only preventing files from being published to an Azure Function, rather than preventing them from being committed.For example, with a project structure such as this:
Where
.funcignore
contains this:After using VSCode to deploy the function, in the
Code & Test
window we seeMyFunctionApp\ExampleFunction1\confidential.secret
exists in the app's directory.The same issue is mentioned here on the related Azure Functions Github Action thread: Azure/functions-action#36 (comment)
The text was updated successfully, but these errors were encountered: