Det er opprettet to brancher i vårt github repo. Develop branch som holder kode for dev miljøet. Master branch som holder kode for test og prod miljøet. Det er implementert regler som krever at man setter opp PR, og for å kunne merge koden til develop må en annen utvikler godkjenne koden. Det er også implementert build check som starter automatisk når man setter opp PR, slik at man unngår å merge inn kode som vil feile i CICD.
Github branch policyPR to master with build check
Mappestruktur
/nINjas
Inneholder vår SPA applikasjon med React og .NET6
/nINjas.Infrastructure
Inneholder ASP.NET med Pulumi
/python
Inneholder pyton kode for å ta bilde med rasbery pi og analysering av bilde
Infrastructure as code with Pulumi
Pulumi with ASP.NET
CICD as code with yaml
Deployment with the power of the shell
Vi har jobbet med å kjøre CICD i azure devops men har noen rettighetsproblemer så deployment er gjort med powershell:
Deploy infrastructure with pulumi commands in powershellFailed deployment in AzureDevops but with more time it will work!
Our Blazor web app allows people to register as Turtles, meaning they will help others in need. In the field, Turtles use the official Dynamics mobile app. To use the official app, users need an Azure AD user with a Dynamics license and a security role in Dynamics.
Instead of having to manually create users in Azure AD and assign licenses and Dynamics security roles, this infrastructure is programmatically set up.
The backend of the Blazor web app uses a custom Azure API client which programmatically sets up the infrastructure: creation of Azure AD users and assigning of Dynamics licenses.
Because of our Infrastructure as Code, users are able to use the official Dynamics mobile app automatically after registering – no manual steps required!
The following image shows the method that creates an Azure AD user and assigns the Dynamics license.
Interaction with Azure AD is done using GraphServiceClient from the Microsoft.Graph NuGet package. Authentication is done using an Access Token retrieved using functionality from the Microsoft.Identity NuGet package.
In order to ship our components from development to prodction we have leveraged several technologies.
Dataverse
In order to export our solution for dataverse we have built a set of yaml based pipelines in azure devops. We have isolated the tasks to their own separate template files which are then called when needed, allowing for simple reuse of functionality.
Azure
To deploy our azure resources we have used bicep instead of armtemplates. These are leveraged in azure devops pipelines. We have created templates for the individual types of components as illustrated below.
Working this way is best practise for Application Lifecycle Management (ALM) and makes it possible to deploy portals to dev, test and production in a painful and fluent way.
Powershell with Portals CLI
We use PowerShell to handle Portals commands to authenticate, create auth profiles, download and upload portal content. This enables us to use Visual Studio Code when working with Portals code.
We are now ready with CI/CD in our solution. All resources are now defined and implemented via arm templates, it improves the deployment process to the different environments.
We defined first our build pipeline in DevOps:
Once the build is completed, the RELEASE pipeline runs and deploys resources to our Resource Group
Iterating on the light/dark theme upload scripts TMNT IT management has added the capability to iterate over all SharePoint sites and apply the dark theme as default.
The updated script https://github.com/EivindBerge/PIZZA-TIME-ACDC-2022/blob/main/theming/site-theme-management-tmnt.ps1 is running in a scheduled Azure Run Book using PowerShell Core 7.1. SharePoint Online Credentials are as runbook credentials, which is sufficient for this scenario. Key Vault could of course be an option, or even better using a certificate – but as IT is very centralized this works for the time being.
CredentialRunbookA job well doneInverted theme applied!
We have also added more code and security scanning tools to also cover PowerShell scripts and find more general security issues.
Ever wondered where your dog are when there’s no food around? How about asking Cortana, Siri, Alexa, or even better Boten Anna?
We have created an integrated solution, with CI/CD in Azure Devops, Cognitive Services, Azure Functions and Power Virtual Agent.
The solution starts with an Azure Function written in Visual Studio.
When code is completed, committed and Pull Requested into the main branch, our CICD pipeline (YML) fires and pushes the solution to Azure Functions
The Azure function is running with a set of pre-captured surveillance images (Due to GDPR we are not using live video). Each folder consists of three photos, one from the kitchen, one from the hallway and one from the livingroom.
Azure Blob storage
Each of these photos will be evaluated with the cognitive service vision functionality. Each of the evaulated photos will be returned with an url for the user to check, and with a textual answer to where the dog is actually located.
It’s important to keep branding consistent across SharePoint Sites. Family members can create travel sites and it will be provisioned with the correct colors, icons and travel lists.
We have crated a Site Script and a site design and deployed it to the SharePoint site for D365 Family Engagement Hub. When a family is planing a new vaication or travel they can create a new site that already have lists they need to plan their stay.
Site Script
First we set the script by identifying the lists with name, description and fields.
Then the final line to add the script
Add-SPOSiteScript -Title “Family Travel Site” -Content $site_script -Description “Create a list for to keep up with traveling family memebers”
The response was a site script with ID
The ID we used in the adding a site design with the site script
Add-SPOSiteDesign -Title “D365 Family Engagement Hub – Travel Site” -WebTemplate “64” -SiteScripts “1131785c-864c-4262-a3ae-b2c9664bfcb6” -Description “The travel site is for planning a trip or travel for the family”
Response
The result was a site design that we can use from the user interface or use another live of powershell to set on a site:
This script will exclude access to all users but those who are members of this specific user group (email enabled) “family Members”
Doing the Get to validate that the permissions were set.
When the users NOT in this group try to use the site design they will not see it – making it possible to family users only to access the site script and site design.
