...
The below step will use the MSBuild Plugin to restore the .NET Codebase in the TEMP folder.
...
Step-iii: Build .NET ApplicationThe below step will use the MSBuild Plugin to Build the .NET Application to create the executable filesnote: Each application will have separate directory structure/file name hence the all paths need to be modified accordingly.
note: Its essential to make sure Consumes Artifacts and Produces Artifacts checkbox is marked only when required. Please follow the snapshots for all execution steps to avoid any discrepancy.
Step-iii: Build .NET Application
The below step will use the MSBuild Plugin to Build the .NET Application to create the executable files(.dll etc)
...
Step-iii: Copy the properties file to the intermediate dir
...
If we look inside the deploy.zip, it contains the executable along with other associated files. Basically, it contains all relevant files that need to be copied to the Azure Function App backend. Azure Function App treats this as an executable package and runs it.
...
Notenote: the executable files inside the .zip file shouldn’t be inside any subfolder. Else once the zip file is deployed to Azure Function App may not work.
...
Application Setting and Connection String values will be updated against the Function Slot Name configured at the environment level. Refer to the Deploy to Slot section for further detailsthe environment level. Refer to the Deploy to Slot section for further details.
There could also be scenarios where someone only need to update the Application Setting or Connection String without actually deploying the code. In that case one can use upsertFunctionApplicationSetting or upsertFunctionConnectionString operations respectively. The workflow execution will be exactly same only the code archive creation /Docker image update step will not be required. Build workflow generated artifact should only container AppSetting.json or ConnString.json. These values can also be passed as input as already mentioned in detail in above section.
Target Properties
Select Topology from the menu and then select Topology Overview from the left menu. You will see a table that has Instances as the rows and Environments as the columns with colored circles representing the Environment Instance. Color coding represents:
...
Properties | Mandatory Field | Description |
|---|---|---|
Function Slot Name |
| Target slot for deployment |
Target Slot to swap | Optional | In case slot swap is required |
Azure Cloud Account |
| Azure account with relevant details |
Absolute path of Azure CLI | Optional | Not required if Azure CLI already added to workflow execution m/c class path |
GIT Path | Optional | Path to the Git executable. Required only if git is not on class path. |
Below given are the environment-specific values which need to be updated.
...
Post deployment debugging
Post deployment success from of plugin execution it can take a little while for the function application up and running.
...
Best way to check logs: https://$func_name.scm.azurewebsites.net/api/logstream or logstream from logstream from console. As already in above scenarios.In , in case of failure we can easily debug the issue from log and get the issue fixed.
...