...
Below is a sample build workflow to build .NET publish folder and create an artifact from it.
...
Step-i: Clone Git Repository
This step will clone the Git repository codebase into the project execution working directory. The Git URL will be retrieved from Source Control configured under Project Configuration.
...
Git Codebase
...
Exported Codebase
...
Step-ii: Restore .NET Application
The below step will use the MSBuild Plugin to restore the .NET Codebase in the TEMP folder.
...
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
Application Setting and Connection String json files(if applicable/present) will be moved to the intermediate directory. An intermediate directory can have any name, in this case, we are using the artifactsObjects folder inside the temp directory. File names are mentioned under File Filter with ‘##’ separated(as advised in the description). Application Setting and Connection String values can also be passed as input to deploy workflow. Application Setting and Connection String files are optional, please review the Application Setting and Connection String property update for a detailed explanation.
...
Step-v: Create an archive of the executable in the intermediate dir
Per the Azure Function App deployment requirement, we have created an archive with the .NET executable inside it.
...
Note: 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.
Step-v: Save all as Artifact from the intermediate dir
Post execution of the above steps the intermediate directory(artifactObjects) should contain files as shown below.
...
As part of the above step, all files inside the artifactObjects folder are archived to create an artifacts.zip which will be saved as an artifact for future reference from the Deployment workflow.
...
The deployFunctions operation returns four output variables. To capture them and use them for further processing/evaluation, one can create four variables and map them against the output parameters of deployFunctions operation. Return As Output option should be checked.
First, click the X2 button to open the Variables popup.
Next use Create option to add four output variables.
...
Please refer to this link for the input structure of Application Setting and Connection String both when passed as a file or as input parameter - Application Setting/Connection String file and input content acceptable structure
In case both the Application Setting file and Application Setting input argument are passed, a consolidated list of properties will be considered while updating Function App. In case the same attribute is used both in the file and input, the value provided as part of the input will take precedence. The same applies to Connection String as well.
...
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:
...
Best way to check logs: https://$func_name.scm.azurewebsites.net/api/logstream or logstream from console. As already in above scenarios, in case of failure we can easily debug the issue from log and get the issue fixed.
...