DEV Community: Arindam Mitra

The Art of Iteration: Loop in Pipeline Stage

Arindam Mitra — Sat, 04 Jan 2025 16:04:15 +0000

Greetings my fellow Technology Advocates and Specialists.

This is the Chapter #2 of my Mastering Loops in Azure DevOps Series.

In this Session, I will walk you through The Art of Iteration: Loop in Pipeline Stage.

USECASE:-
Validate and Provision Multiple Azure Resource Groups using Iterations in an Azure DevOps YAML Pipeline.

IMPORTANT NOTE:-

The YAML Pipeline is tested on WINDOWS BUILD AGENT Only!!!

REQUIREMENTS:-

Azure Subscription.
Azure DevOps Organisation and Project.
Service Principal with Required RBAC (Contributor) applied on Subscription or Resource Group(s).
Azure Resource Manager Service Connection in Azure DevOps.

CODE REPOSITORY:-

arindam0310018 / 03-Jan-2025-DevOps__Mastering-Loops-in-Azure-DevOps

MASTERING LOOPS IN AZURE DEVOPS

Mastering Loops in Azure DevOps:-

Greetings to my fellow Technology Advocates and Specialists.

This is "Mastering Loops in Azure DevOps" Series !

DATE	TOPICS	CONTENT
03.01.2025	The Art of Iteration: Starting the Cycle	https://dev.to/arindam0310018/the-art-of-iteration-starting-the-cycle-1op
04.01.2025	The Art of Iteration: Loop in Pipeline Stage	https://dev.to/arindam0310018/the-art-of-iteration-loop-in-pipeline-stage-40he

View on GitHub

HOW DOES MY CODE PLACEHOLDER LOOKS LIKE:-:-

EXAMPLE:-

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-Leverage-Loops-For-Automation-v1.0.yml):-

trigger:
  none

######################
#DECLARE PARAMETERS:-
######################
parameters:
- name: SUBSCRIPTIONID
  displayName: Subscription ID Details Follow Below:-
  type: string
  default: 210e66cb-55cf-424e-8daa-6cad804ab604
  values:
  - 210e66cb-55cf-424e-8daa-6cad804ab604

- name: RGNAME
  displayName: Please Provide the Resource Group Name:-
  type: object
  default: [AMRG001,AMRG002,AMRG003]

######################
#DECLARE VARIABLES:-
######################
variables:
  ServiceConnection: amcloud-cicd-service-connection
  BuildAgent: windows-latest
  loc: westeurope

#########################
# Declare Build Agents:-
#########################
pool:
  vmImage: $(BuildAgent)

###################
# Declare Stages:-
###################

stages:
- ${{ each rg in parameters.RGNAME }}:
  - stage: VALIDATE_AND_CREATE_${{ rg }} 
    jobs:
    - job: VALIDATE_AND_CREATE_${{ rg }} 
      displayName: VALIDATE AND CREATE ${{ rg }}
      steps:
      - task: AzureCLI@2
        displayName: SET AZURE ACCOUNT
        inputs:
          azureSubscription: $(ServiceConnection)
          scriptType: ps
          scriptLocation: inlineScript
          inlineScript: |
            az --version
            az account set --subscription ${{ parameters.SUBSCRIPTIONID }}
            az account show  
      - task: AzureCLI@2
        displayName: VALIDATE AND CREATE ${{ rg }}
        inputs:
          azureSubscription: $(ServiceConnection)
          scriptType: ps
          scriptLocation: inlineScript
          inlineScript: |      
            echo "Looped Value is: "${{ rg }}""

            $i = az group exists -n ${{ rg }}
              if ($i -eq "true") {
                echo "#####################################################"
                echo "Resource Group ${{ rg }} exists!!!"
                echo "#####################################################"
                }
                else {
                  echo "#############################################################"
                  echo "Resource Group ${{ rg }} DOES NOT EXISTS!!!"
                  echo "#############################################################"
                  echo "Creating Resource Group ${{ rg }}..."
                  echo "#############################################################"
                  az group create --name ${{ rg }} --location $(loc)
                  echo "#############################################################"
                  echo "Resource Group ${{ rg }} Successfully"
                  echo "#############################################################"
                }

EXPLANATION:-

I.) It is a Single Stage Pipeline which first validates if Resource Group by the same name is available. If "No", then it will go ahead and create. If "Yes", it will then display in the pipeline console that "Resource Group Exists".

II.) Declare "Parameter" of type "Object". In this example, I have declared 3 values (Resource Group Names) as an array.

######################
#DECLARE PARAMETERS:-
######################
parameters:
- name: SUBSCRIPTIONID
  displayName: Subscription ID Details Follow Below:-
  type: string
  default: 210e66cb-55cf-424e-8daa-6cad804ab604
  values:
  - 210e66cb-55cf-424e-8daa-6cad804ab604

- name: RGNAME
  displayName: Please Provide the Resource Group Name:-
  type: object
  default: [AMRG001,AMRG002,AMRG003]

III.) Declare "Each" at beginning of the Pipeline stage. The "rg" variable stores all the values that the "each" keyword iterates over in the parameter of type object.

stages:
  - ${{ each rg in parameters.RGNAME }}:

IV.) As there are 3 values declared in "Parameter" of type "Object", there will be 3 STAGES CREATED.

V.) Name of each stage and job will be one of iterated value from the array declared in "Parameter" of type "Object".

- stage: VALIDATE_AND_CREATE_${{ rg }} 
    jobs:
    - job: VALIDATE_AND_CREATE_${{ rg }} 
      displayName: VALIDATE AND CREATE ${{ rg }}

VI.) Validation of the iterated value from the array declared in "Parameter" of type "Object" followed by the decision, whether to create Resource Group or not, happens as part of Inline Script.

- task: AzureCLI@2
        displayName: VALIDATE AND CREATE ${{ rg }}
        inputs:
          azureSubscription: $(ServiceConnection)
          scriptType: ps
          scriptLocation: inlineScript
          inlineScript: |      
            echo "Looped Value is: "${{ rg }}""

            $i = az group exists -n ${{ rg }}
              if ($i -eq "true") {
                echo "#####################################################"
                echo "Resource Group ${{ rg }} exists!!!"
                echo "#####################################################"
                }
                else {
                  echo "#############################################################"
                  echo "Resource Group ${{ rg }} DOES NOT EXISTS!!!"
                  echo "#############################################################"
                  echo "Creating Resource Group ${{ rg }}..."
                  echo "#############################################################"
                  az group create --name ${{ rg }} --location $(loc)
                  echo "#############################################################"
                  echo "Resource Group ${{ rg }} Successfully"
                  echo "#############################################################"
                }

OUTPUT OF EXAMPLE:-
1. As in the example, there were 3 values declared in "Parameter" of type "Object", hence 3 STAGES got created.

2. Name of each stage and Job is the iterated value from the array declared in "Parameter" of type "Object".

3. Below is how it looks when the Pipeline iterates and creates resource group(s).

4. Below is how it looks when the pipeline iterates, detects that a resource group with the same name already exists, and therefore skips creating the resource group(s).

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

The Art of Iteration: Starting the Cycle

Arindam Mitra — Fri, 03 Jan 2025 21:54:40 +0000

Greetings my fellow Technology Advocates and Specialists.

This is the Chapter #1 of my Mastering Loops in Azure DevOps Series.

In this Session, I will walk you through The Art of Iteration: Starting the Cycle.

This is a quick start guide to introduce the topic and how it is relevant to the real world.

IMPORTANT NOTE:-

The YAML Pipeline is tested on WINDOWS BUILD AGENT Only!!!

REQUIREMENTS:-

Azure Subscription.
Azure DevOps Organisation and Project.
Service Principal with Required RBAC (Contributor) applied on Subscription or Resource Group(s).
Azure Resource Manager Service Connection in Azure DevOps.

CODE REPOSITORY:-

arindam0310018 / 03-Jan-2025-DevOps__Mastering-Loops-in-Azure-DevOps

MASTERING LOOPS IN AZURE DEVOPS

Mastering Loops in Azure DevOps:-

Greetings to my fellow Technology Advocates and Specialists.

This is "Mastering Loops in Azure DevOps" Series !

DATE	TOPICS	CONTENT
03.01.2025	The Art of Iteration: Starting the Cycle	https://dev.to/arindam0310018/the-art-of-iteration-starting-the-cycle-1op
04.01.2025	The Art of Iteration: Loop in Pipeline Stage	https://dev.to/arindam0310018/the-art-of-iteration-loop-in-pipeline-stage-40he

View on GitHub

REFERENCE LINKS:-
1. Microsoft Learn - Azure Devops - Expressions.

HOW DOES MY CODE PLACEHOLDER LOOKS LIKE:-:-

MILLION DOLLAR QUESTION:-
Question: Can we use "Loop" in Azure Devops YAML Pipeline ?
Answer: YES

HOW ?
Concise summary follows below:-
1.) We can use "Loop" in Azure Devops YAML Pipeline by using the "each" keyword.
2.) We can use the "each" keyword to loop through a) Parameters with the type as b) Object.
3.) Additionally, you can iterate through Nested elements within an Object.

EXAMPLE:-

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-Leverage-Loops-For-Automation-Initial-Test.yml):-

trigger:
  none

######################
#DECLARE PARAMETERS:-
######################
parameters:
- name: RGNAME
  displayName: Please Provide the Resource Group Name:-
  type: object
  default: [AMRG001,AMRG002,AMRG003]

######################
#DECLARE VARIABLES:-
######################
variables:
  BuildAgent: windows-latest

#########################
# Declare Build Agents:-
#########################
pool:
  vmImage: $(BuildAgent)

###################
# Declare Stages:-
###################
stages:
  - ${{ each rg in parameters.RGNAME }}:
    - stage: CREATE_${{ rg }}
      jobs:
        - job: CreateResourceGroup
          steps:
            - script: echo "Creating "${{ rg }}""

EXPLANATION:-

I.) Declare "Parameter" of type "Object". In this example, I have declared 3 values (Resource Group Names) as an array.

######################
#DECLARE PARAMETERS:-
######################
parameters:
- name: RGNAME
  displayName: Please Provide the Resource Group Name:-
  type: object
  default: [AMRG001,AMRG002,AMRG003]

II.) Declare "Each" at beginning of the Pipeline stage. The "rg" variable stores all the values that the "each" keyword iterates over in the parameter of type object.

stages:
  - ${{ each rg in parameters.RGNAME }}:

III.) As there are 3 values declared in "Parameter" of type "Object", there will be 3 STAGES CREATED.

IV.) Name of each stage will be one of iterated value from the array declared in "Parameter" of type "Object".

- stage: CREATE_${{ rg }}

V.) Finally, each stage displays the Value in the console.

steps:
            - script: echo "Creating "${{ rg }}""

OUTPUT OF EXAMPLE:-
1. As in the example, there were 3 values declared in "Parameter" of type "Object", hence 3 STAGES got created.

2. Name of each stage is the iterated value from the array declared in "Parameter" of type "Object".

3. Each stage displays the Value in the console.
STAGE #1: CREATE_AMRG001

STAGE #2: CREATE_AMRG002

STAGE #3: CREATE_AMRG003

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Dropdown or Radio button options in Azure Devops

Arindam Mitra — Wed, 01 Jan 2025 21:53:20 +0000

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate Dropdown OR Radio button options in Azure Devops.

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Radio Button option as Runtime Variables in Azure Devops Pipelines.
2.	Dropdown Menu option as Runtime Variables in Azure Devops Pipelines.
3.	Spot the difference.

IMPORTANT NOTE:-

The YAML Pipeline is tested on WINDOWS BUILD AGENT Only!!!

REQUIREMENTS:-

Azure Subscription.
Azure DevOps Organisation and Project.
Service Principal with Required RBAC ( Contributor) applied on Subscription or Resource Group(s).
Azure Resource Manager Service Connection in Azure DevOps.

CODE REPOSITORY:-

arindam0310018 / 01-Jan-2025-DevOps__Dropdown-or-Radio-button-options-in-Azure-Devops

Dropdown or Radio button options in Azure Devops

Dropdown or Radio button options in Azure Devops:-

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate Dropdown OR Radio button options in Azure Devops.

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Radio Button option as Runtime Variables in Azure Devops Pipelines.
2.	Dropdown Menu option as Runtime Variables in Azure Devops Pipelines.
3.	Spot the difference.

IMPORTANT NOTE:-

The YAML Pipeline is tested on WINDOWS BUILD AGENT Only!!!

REQUIREMENTS:-

Azure Subscription.
Azure DevOps Organisation and Project.
Service Principal with Required RBAC ( Contributor) applied on Subscription or Resource Group(s).
Azure Resource Manager Service Connection in Azure DevOps.

HOW DOES MY CODE PLACEHOLDER LOOKS LIKE:-

1. RADIO BUTTON OPTION AS RUNTIME VARIABLES:-

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-runtime-parameter-options-v1.0.yml):-

trigger
  none

##################
# Radio Button:-
##################
parameters:
  - name: environment
    displayName: Select environment
    type: string
    default: 'dev'
    values:
      - dev
      - test
      - uat

#############
#Variables:-

…

View on GitHub

HOW DOES MY CODE PLACEHOLDER LOOKS LIKE:-

1. RADIO BUTTON OPTION AS RUNTIME VARIABLES:-

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-runtime-parameter-options-v1.0.yml):-

trigger:
  none

##################
# Radio Button:-
##################
parameters:
  - name: environment
    displayName: Select environment
    type: string
    default: 'dev'
    values:
      - dev
      - test
      - uat

#############
#Variables:-
############
variables:
  ServiceConnection: 'amcloud-cicd-service-connection' # Please replace with your Service Connection!
  BuildAgent: 'windows-latest' # Please replace with your Build Agent. You can continue to use this as this is Microsoft Hosted Windows Build Agent!

######################
# Declare Build Agent:-
######################
pool:
  vmImage: '$(BuildAgent)'

##################################
# Declare Stages:-
# Test Runtime parameters as:-
# 1. Radio Button
##################################
stages:
- stage: Test_Runtime_Parameters_RadioButton
  displayName: Test Runtime Parameters Radio Button
  jobs:
  - job: Test_Runtime_Parameters_RadioButton
    steps:
    - task: AzureCLI@2
      displayName: Test Runtime Parameters RadioButton
      inputs:
        azureSubscription: '$(ServiceConnection)'
        scriptLocation: 'inlineScript'
        scriptType: 'ps'
        inlineScript: |
          echo "Deploying to ${{ parameters.environment }} environment"

CODE BLOCK FOR RADIO BUTTON AS RUNTIME VARIABLES IN YAML:-

##################
# Radio Button:-
##################
parameters:
  - name: environment
    displayName: Select environment
    type: string
    default: 'dev'
    values:
      - dev
      - test
      - uat

OUTPUT: RADIO BUTTON OPTION AS RUNTIME VARIABLES
1. Radio Button as runtime variables is displayed successfully on Pipeline Execution.

2. Successful Pipeline Execution.

2. DROPDOWN MENU OPTION AS RUNTIME VARIABLES:-

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-runtime-parameter-options-v1.1.yml):-

trigger:
  none

##################
# Drop Down Menu:-
##################
parameters:
  - name: environment
    displayName: Select environment
    type: string
    default: 'dev'
    values:
      - dev
      - test
      - uat
      - prod

#############
#Variables:-
############
variables:
  ServiceConnection: 'amcloud-cicd-service-connection' # Please replace with your Service Connection!
  BuildAgent: 'windows-latest' # Please replace with your Build Agent. You can continue to use this as this is Microsoft Hosted Windows Build Agent!

######################
# Declare Build Agent:-
######################
pool:
  vmImage: '$(BuildAgent)'

##################################
# Declare Stages:-
# Test Runtime parameters as:-
# 1. Dropdown Menu
##################################
stages:
- stage: Test_Runtime_Parameters_DropDown_Menu
  displayName: Test Runtime Parameters Dropdown Menu
  jobs:
  - job: Test_Runtime_Parameters_DropDown_Menu
    steps:
    - task: AzureCLI@2
      displayName: Test Runtime Parameters Dropdown Menu
      inputs:
        azureSubscription: '$(ServiceConnection)'
        scriptLocation: 'inlineScript'
        scriptType: 'ps'
        inlineScript: |
          echo "Deploying to ${{ parameters.environment }} environment"

CODE BLOCK FOR DROPDOWN MENU AS RUNTIME VARIABLES IN YAML:-

##################
# Drop Down Menu:-
##################
parameters:
  - name: environment
    displayName: Select environment
    type: string
    default: 'dev'
    values:
      - dev
      - test
      - uat
      - prod

OUTPUT: DROPDOWN MENU OPTION AS RUNTIME VARIABLES
1. Dropdown Menu as runtime variables is displayed successfully on Pipeline Execution.


2. Successful Pipeline Execution.

3. SPOT THE DIFFERENCE:-
The "type" of the variable is exactly the same except the no. of values. For "Radio button", we entered 3 values but if we needed "Dropdown Menu", we just increased 1 more value. "Radio button" option changes to "Dropdown Menu".
For "Radio button", value count <= 3
For "Dropdown Menu", value count > 3

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

OpenAI Operational Status

Arindam Mitra — Fri, 27 Dec 2024 19:46:40 +0000

Greetings my fellow Technology Advocates and Specialists.

This is the Chapter #7 of my Data & AI Series based on my recent learning.

In this Session, I will share my recent learning on OpenAI Operational Status.

ADDITIONAL CONTRIBUTOR(S):-
Tanushri Nayak

CODE REPOSITORY:-

arindam0310018 / 09-May-2024-Data-And-AI__All-In-One

DATA & AI

Data And AI with Azure - All in One:-

Greetings to my fellow Technology Advocates and Specialists.

The Objective of this series is to learn as much as possible on Data and AI and in the process help others.

DATE	TOPICS	CONTENT
09.05.2024	Recap: Microsoft Build AI Day Switzerland 2024	https://dev.to/arindam0310018/recap-microsoft-build-ai-day-switzerland-2024-2b62
12.05.2024	Microsoft OpenAI Architecture	https://dev.to/arindam0310018/microsoft-openai-architecture-2i35
12.05.2024	Microsoft OpenAI Security	https://dev.to/arindam0310018/microsoft-openai-security-5ej6
12.05.2024	Readiness of Organisation for AI Adoption	https://dev.to/arindam0310018/readiness-of-organisation-for-ai-adoption-4eli
12.05.2024	Microsoft OpenAI: Errors I Learned	https://dev.to/arindam0310018/microsoft-openai-errors-i-learned-f4k
17.08.2024	Tactiq - ChatGPT Meeting Summary	https://dev.to/arindam0310018/tactiq-chatgpt-meeting-summary-2942
27.12.2024	OpenAI Operational Status	https://dev.to/arindam0310018/openai-operational-status-4afh

View on GitHub

On 26th December 2024, ChatGPT was NOT operational. That triggered the question - "How to validate the OpenAI operational status ?"

VALIDATE OPENAI OPERATIONAL STATUS:-
https://status.openai.com/

STATUS ON 26th DECEMBER 2024:-
High Error Rates on ChatGPT, API and SORA.

FULL DETAILS ON 26th DECEMBER 2024 OPENAI OUTAGE:-
Below screenshot is taken from: https://status.openai.com/

OPENAI FULL OPERATIONAL MODE:-
Below screenshot show how OpenAI is Fully Operational.

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Rule of Thumb for spinning up Azure Landing Zones

Arindam Mitra — Fri, 27 Dec 2024 18:51:29 +0000

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will provide my understanding on Rule of Thumb for spinning up Azure Landing Zones.

#	OBJECTIVES
1.	THE WHAT: What is the Purpose of Rule of Thumb for spinning up Azure Landing Zones ?
2.	THE WHY: Why is the Rule of Thumb for spinning up Azure Landing Zones required ?
3.	THE HOW: How to define Rule of Thumb for spinning up Azure Landing Zones required ?

CODE REPOSITORY:-

arindam0310018 / 27-Dec-2024-Azure__Rule-of-Thumb-for-spinning-up-Azure-Landing-Zones

Rule of Thumb for spinning up Azure Landing Zones

Rule of Thumb for spinning up Azure Landing Zones:-

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will provide my understanding on Rule of Thumb for spinning up Azure Landing Zones.

#	OBJECTIVES
1.	THE WHAT: What is the Purpose of Rule of Thumb for spinning up Azure Landing Zones ?
2.	THE WHY: Why is the Rule of Thumb for spinning up Azure Landing Zones required ?
3.	THE HOW: How to define Rule of Thumb for spinning up Azure Landing Zones required ?

THE WHAT ?
Your organisation may have branch offices or subsidiaries spread across multiple countries.

THE WHY ?
Azure Landing Zones should be provisioned in regions closest to where the workloads are deployed, But there needs to be some guidelines/principles otherwise we would have Landing Zones in every region.

THE HOW ?
For this Article, we considered all Azure Data Centers

…

View on GitHub

THE WHAT ?
Your organisation may have branch offices or subsidiaries spread across multiple countries.

THE WHY ?
Azure Landing Zones should be provisioned in regions closest to where the workloads are deployed, But there needs to be some guidelines/principles otherwise we would have Landing Zones in every region.

THE HOW ?
For this Article, we considered all Azure Data Centers in Europe: AZURE EUROPE REGIONS.

#	REGIONS	CITY
1.	France Central	Paris
2.	France South	Marseille
3.	Germany Central	Frankfurt
4.	Germany North	Berlin
5.	Germany Northeast	Magdeburg
6.	Germany West Central	Frankfurt
7.	Greece Central	Athens
8.	North Europe	Dublin
9.	West Europe	Amsterdam
10.	Italy North	Milan
11.	Norway East	Oslo
12.	Norway West	Stavanger
13.	Poland Central	Warsaw
14.	Spain Central	Madrid
15.	Sweden Central	Gavle
16.	Sweden South	Staffanstorp
17.	Switzerland North	Zurich
18.	Switzerland West	Geneva
19.	UK South	London
20.	UK West	Cardiff

RULE OF THUMB:-

#	CRITERIA	DETAILS	PRIORITY OF THE CRITERIA	REMARKS
1.	Requirement from No. of Projects ?	-	P1	-
2.	Anticipating Potential Future Region Trends.	-	P1	Coordinating with Internal Stakeholders if the potential future region(s) can be used to the maximum.
3.	Availability Zones.	If the Region Supports Availability Zones to provide higher Availability across multiple Zones.	P1	Not all regions have three availability zones upon launch.
4.	Business Continuity and Disaster Recovery.	If the region may not have a paired region, which could impact replication and disaster recovery strategies.	P1	-
5.	Scalability.	Region may have limited capacity to scale resources.	P1	-
6.	Cost.	Review the cost model as prices of Azure Services can vary between Regions.	P1	-
7.	Data Transfer.	Data Transfer between regions incur additional costs.	P1	Evaluate Operational Impact. Time to migrate date depends upon - a.) Network Speed; and b.) Volume of Data.
8.	Performance.	Test the Latency and Network Performance from Application to meet the required performance standards.	P1	-
9.	SLA.	SLAs are adjusted until they reach full operational maturity.	P2	This is not for all Azure Services but Few.
10.	Data Residency and Compliance.	Region should meet Compliance and Regulatory of the Organisation Domain.	P2	-
11.	Sustainability.	Region operates on renewable energy Sources.	P2	Microsoft emphasizes on sustainable data centers.

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Code Generated Architecture Diagram using Azure Devops

Arindam Mitra — Tue, 19 Nov 2024 18:58:26 +0000

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate How to Create Azure Solutions Architecture Diagram by Code using Azure Devops.

I had the Privilege to talk on this topic in ONE Azure Community:-

NAME OF THE AZURE COMMUNITY	TYPE OF SPEAKER SESSION
Festive Tech Calendar - 2024	Virtual

EVENT ANNOUNCEMENTS:-

VIRTUAL SESSION:-
LIVE DEMO was Recorded as part of my Presentation in FESTIVE TECH CALENDAR - 2024 Forum/Platform
Duration of My Demo = 49 Mins 02 Secs

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Example #1: Create "Basic Azure App Service Architecture Diagram" by Code using Azure Devops.
2.	Example #2: Create "Gaming Architecture Diagram" by Code using Azure Devops.

IMPORTANT NOTE:-

The YAML Pipeline is tested on WINDOWS BUILD AGENT Only!!!

REQUIREMENTS:-

Azure Subscription.
Azure DevOps Organisation and Project.
System Access Token Configured for Pipeline.
Service Principal with Required RBAC ( Contributor) applied on Subscription or Resource Group(s).
Azure Resource Manager Service Connection in Azure DevOps.

REFERENCE LINKS:-
1. Diagram as Code
2. Diagram as Code - Installation
3. Diagram as Code - Examples
4. Diagram as Code - List of Azure Providers

PRE-REQUISITES:-
1. Python 3.6 or higher.
2. Graphviz
3. pip

CODE REPOSITORY:-
Direct Link to Code!

arindam0310018 / 31-July-2024-DevOps__Diagram-As-Code

DIAGRAM AS CODE

Diagram As Code:-

Greetings to my fellow Technology Advocates and Specialists.

This is "Diagram As Code" Series !

DATE	TOPICS	CONTENT
01.08.2024	Visualizing Cloud Designations with Mermaid	https://dev.to/arindam0310018/visualizing-cloud-designations-with-mermaid-3bl
15.08.2024	Code Generated Architecture Diagram	https://dev.to/arindam0310018/code-generated-architecture-diagram-13o3
19.11.2024	Code Generated Architecture Diagram using Devops	https://dev.to/arindam0310018/code-generated-architecture-diagram-using-azure-devops-2ah4

I had the Privilege to talk on this topic in ONE Azure Communities:-

NAME OF THE AZURE COMMUNITY	TYPE OF SPEAKER SESSION
Festive Tech Calendar - 2024	Virtual

EVENT ANNOUNCEMENTS:-

View on GitHub

HOW DOES MY CODE PLACEHOLDER LOOKS LIKE:-

CONCEPTS:-

I.) DIAGRAMS:-
1. Represents a global diagram context.
2. Diagram context can be created with Diagram class.
3. The first parameter of Diagram constructor will be used for output filename.

II.) NODES:-
1. Represents a single system component object.
2. A node object consists of three parts: i) Provider, ii) Resource type and iii) Name.

III.) CLUSTERS:-
1. Allows you group (or clustering) the nodes.

IV.) EDGES:-
1. Represents a connection between Nodes with some additional properties.

Now, we proceed in Creating Architecture Diagram using Diagrams, Python and Azure Devops.

EXAMPLE #1:

Create "Basic Azure App Service Architecture Diagram" by Code.

CONSTRUCT OF THE PYTHON CODE TO CREATE ARCHITECTURE DIAGRAM:-
1. Import Diagram, Cluster and Edge.
2. Import the Provider Icons for creating diagrams.
3. Creating the building blocks using Nodes and Cluster.
4. Connect the building blocks using Edges.

PYTHON CODE SNIPPET:-

PYTHON CODE (Generate-Basic-Azure-App-service-Arch-Diagram.py):-

############################################################
## Architecture Diagram: Basic Azure App Service:-

## Components include:-
# 1. User
# 2. Azure Entra ID
# 3. Azure Monitor
# 4. Azure Application Insights
# 5. Azure User Assigned Managed Identity
# 6. Azure Key Vault 
# 7. Azure App Services
# 8. Azure SQL Servers

############################################################

######################################################
# Import Diagram, Cluster and Edge.
# Import the Provider Icons for creating diagrams.
######################################################

from diagrams import Cluster, Diagram, Edge
from diagrams.azure.general import Helpsupport, Servicehealth
from diagrams.azure.devops import ApplicationInsights
from diagrams.azure.security import KeyVaults
from diagrams.azure.identity import ManagedIdentities, ActiveDirectory
from diagrams.azure.compute import AppServices
from diagrams.azure.database import SQLServers

#########################################################
# Creating the building blocks using Nodes and Cluster.
#########################################################

with Diagram("Basic Azure App Service Architecture", show=False, direction="TB"):
    usr = Helpsupport("User")

    with Cluster("Compute"):
        components_webapp = [AppServices("AppServices"), KeyVaults("KV"), ManagedIdentities("UMID")]

    with Cluster("Data"):
        components_db = SQLServers("Azure SQL Database")

    with Cluster("Identity"):
        components_identity = [ActiveDirectory("Microsoft Entra ID")]

    with Cluster("Monitoring"):
        components_monitor = [ApplicationInsights("App Insights"), Servicehealth("Azure Monitor")]

############################################
# Connect the building blocks using Edges.
############################################

    usr >> Edge(color="darkorange") >> components_webapp

    components_webapp >> Edge(color="darkgreen") >> components_db

CONSTRUCT OF AZURE DEVOPS PIPELINE TO EXECUTE PYTHON CODE TO CREATE ARCHITECTURE DIAGRAM:-
1. Generate Solution Architecture Diagram using Diagrams, Python and Azure Devops.
2. Commit the Solution Architecture Diagram created to GIT repository.
3. The Pipeline has 2 stages.
4(a). Stage #1 performs below:-
4(b). Install Requisites in the build agent.
4(c). Generate Solution Architecture diagram.
4(d). Copy Generated Solution Architecture diagram to Artifacts staging directory.
4(e). Publish Generated Solution Architecture diagram as Artifacts.
5(i). Stage #2 performs below:-
5(ii). Download Artifacts.
5(iii). Commit Generated Solution Architecture diagram to Azure Devops GIT repository.
5(iv). System Access Token is configured to run the build.

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-diagram-as-code-v1.0.yml):-

####################################
# Automation Scope:-
#####################
# 1. Generate Diagrams by Code.
# 2. Commit 2 Git.
####################################

################################################################################################################################
# Important to Note:-
#####################
# 1. The Consumers only need to change the value which are commented in the "Declare Variables" Section.
# 2. If you are changing the value of "pythonCode" Variable, then make sure, you change the value of "DiagramName" Variable. 
################################################################################################################################

trigger:
  none

#######################
# Declare Variables:-
#######################
variables:
  ServiceConnection: 'amcloud-cicd-service-connection' # Please replace with your Service Connection!
  BuildAgent: 'windows-latest' # Please replace with your Build Agent. You can continue to use this as this is Microsoft Hosted Windows Build Agent!
  envName: 'NonProd' # Please replace with your Azure Devops Environment Name
  pythonCode: 'Generate-Basic-Azure-App-service-Arch-Diagram.py' # Please replace with your script name kept in the "Code" Directory! 
  RootWorkingFolderName: 'Digram-As-Code-With-Devops' # Please replace with your Root Working Folder Name!
  ChildWorkingFolderName1: 'Code' # Please replace with your Child Working Folder Name!
  ChildWorkingFolderName2: 'Diagrams' # Please replace with your Child Working Folder Name!
  WorkingDir: '$(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)' 
  TargetFolderName: 'AMDaC' # Please replace with your naming convention!
  Target: '$(build.artifactstagingdirectory)\$(TargetFolderName)'
  Artifact: 'DaC' # Please replace with your naming convention!
  DiagramName: 'basic_azure_app_service_architecture.png' # Please replace with the name, you have mentioned inside your Python Script!
  DevopsOrgName: 'ArindamMitra0251' # Please replace with your Azure Devops Organisation Name!
  DevopsPrjName: 'AMCLOUD' # Please replace with your Azure Devops Project Name!
  DevopsRepoName: 'YAML-v1.0' # Please replace with your Azure Devops Repository Name!
  DevOpsGITUser: 'AM' # Please replace with your Custom GIT Username!
  DevOpsGITEmail: 'arindam0310018@gmail.com' # Please replace with your GIT user email address!

######################
# Declare Build Agent:-
######################
pool:
  vmImage: '$(BuildAgent)'

#############################
# Declare Stages:-
# Generate Diagrams by Code
#############################
stages:

- stage: Diagram_As_Code
  jobs:
  - job: Diagram_As_Code
    displayName: Diagram As Code
    steps:
    - task: AzureCLI@2
      displayName: Diagram As Code
      inputs:
        azureSubscription: $(ServiceConnection)
        scriptType: ps
        scriptLocation: inlineScript
        inlineScript: |
          echo "##########################################################"
          $choco_ver = choco -v
          echo "The latest chocolatey version installed is: $choco_ver"
          echo "##########################################################"
          python --version
          echo "#######################################"
          pip --version
          echo "#######################################"
          echo "Installing Graphiz...!"
          echo "#######################################"
          choco install graphviz -y
          echo "#######################################"
          echo "Validate graphviz Installation..."
          echo "########################################"
          sleep 10
          dot -V
          echo "########################################"
          pip install diagrams
          echo "########################################"
          cd $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\
          dir
          echo "########################################"
          python $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\$(pythonCode)   
          cd $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\
          dir
          $outputPath = "$(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\$(DiagramName)"
          if (Test-Path $outputPath) {
             Write-Host "$(DiagramName) created successfully."
             } 
          else {
                Write-Host "$(DiagramName) was NOT created."
                exit 1
                }
          echo "########################################"

###############################################
# Copy Files to Artifacts Staging Directory:-
###############################################
    - task: CopyFiles@2
      displayName: Copy Files Artifacts Staging Directory
      inputs:
        SourceFolder: '$(workingDir)'
        Contents: |
          **/*.png
        TargetFolder: '$(Target)'

# ########################
# # Publish Artifacts:-
# ########################
    - task: PublishBuildArtifacts@1
      displayName: Publish Artifacts
      inputs:
        targetPath: '$(Target)'
        artifactName: '$(Artifact)'     

#############################
# Stage: Commit 2 Code
#############################

- stage: Commit_2_Git
  condition: succeeded('Diagram_As_Code')
  jobs:
  - deployment: 
    displayName: Commit_2_Git
    environment: $(envName)
    pool:
      vmImage: '$(BuildAgent)'
    strategy:
      runOnce:
        deploy:
          steps:
          - checkout: self 
            persistCredentials: true

#########################
# Download Artifacts:-
#########################
          - task: DownloadBuildArtifacts@0
            displayName: Download Artifacts
            inputs:
              buildType: 'current'
              downloadType: 'single'
              artifactName: '$(Artifact)'
              downloadPath: '$(System.ArtifactsDirectory)'

#########################################
# Commit 2 Git:-
# Authentication - System Access Token
#########################################
          - task: PowerShell@2
            displayName: GIT Commit 
            inputs:
              targetType: 'inline'
              script: |
                cd $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName2)
                cp $(System.ArtifactsDirectory)\$(Artifact)\$(TargetFolderName)\$(DiagramName) . 
                echo "#####################"
                echo "Diagram copied!"
                echo "Listing the contents in the current directory:-"
                dir
                echo "#####################"
                git remote -v
                echo "#####################"
                git remote set-url origin https://$(System.AccessToken)@dev.azure.com/$(DevopsOrgName)/$(DevopsPrjName)/_git/$(DevopsRepoName)
                echo "#####################"
                git ls-remote origin
                echo "#####################"
                git config --global user.email "$(DevOpsGITEmail)"
                git config --global user.name "$(DevOpsGITUser)"
                git config --global --unset https.proxy
                git checkout -b $(Build.SourceBranchName)
                git add .
                git commit -m "Output Architecture Diagram"
                git push origin $(Build.SourceBranchName)
            env:
              SYSTEM_ACCESSTOKEN: $(System.AccessToken)

IMPORTANT TO NOTE:-
1. The users only need to change the value which are commented in the "Declare Variables" Section.
2. If you are changing the value of "pythonCode" Variable, then make sure, you change the value of "DiagramName" Variable.

OUTPUT OF EXAMPLE #1:-
1. Configure System Access Token.

2. Successful Pipeline run.

3. Generated Solutions Architecture Diagram as Artifacts Uploaded in Azure Devops.


4. Solutions Architecture Diagram Generated is Committed in Azure Devops Repo.

EXAMPLE #2:

Create "Gaming Architecture Diagram" by Code.

CONSTRUCT OF THE PYTHON CODE TO CREATE ARCHITECTURE DIAGRAM:-
1. Import Diagram, Cluster and Edge.
2. Import the Provider Icons for creating diagrams.
3. Creating the building blocks using Nodes and Cluster.
4. Connect the building blocks using Edges.

PYTHON CODE SNIPPET:-

PYTHON CODE (Generate-Gaming-Arch-Diagrams.py):-

############################################################
## Architecture Diagram: Gaming using Azure Cosmos DB:-

## Components include:-
# 1. User
# 2. Azure Traffic Manager
# 3. Azure Content Delivery Network
# 4. Azure Storage
# 5. Azure API Management 
# 6. Azure Cosmos DB
# 7. Azure Databricks
# 8. Azure Functions
# 9. Azure Notification Hubs

############################################################

######################################################
# Import Diagram, Cluster and Edge.
# Import the Provider Icons for creating diagrams.
######################################################

from diagrams import Cluster, Diagram, Edge
from diagrams.azure.general import Helpsupport
from diagrams.azure.network import TrafficManagerProfiles, CDNProfiles
from diagrams.azure.storage import StorageAccounts
from diagrams.azure.integration import APIManagement
from diagrams.azure.database import CosmosDb
from diagrams.azure.analytics import Databricks
from diagrams.azure.compute import FunctionApps
from diagrams.azure.mobile import NotificationHubs

#########################################################
# Creating the building blocks using Nodes and Cluster.
#########################################################

# with Diagram("GAMING ARCHITECTURE", show=False, direction="TB"):
with Diagram("GAMING ARCHITECTURE", show=False):
    usr = Helpsupport("User")

    # atm = TrafficManagerProfiles("Azure Traffic Manager")

    apim = APIManagement("Azure API Apps")

    cosmos = CosmosDb("Azure Cosmos DB")

    dbks = Databricks("Azure Databricks")

    # cdn = CDNProfiles ("Azure CDN")

    # storage = StorageAccounts("Azure Storage (Media Files)")

    functions = FunctionApps("Azure Functions")

    notifyhub = NotificationHubs("Azure Notification Hubs")

    with Cluster(""):
         atm = TrafficManagerProfiles("Traffic Manager")

    with Cluster(""):
         cdn = CDNProfiles ("Azure CDN")

    with Cluster(""):
         storage = StorageAccounts("Azure Storage")

############################################
# Connect the building blocks using Edges.
############################################

    usr >> Edge(color="darkgreen") >> atm
    cdn >> Edge(color="darkblue") >> atm
    storage >> Edge(color="darkpurple") >> cdn
    atm >> Edge(color="darkorange") >> apim
    apim >> Edge(color="darkred") >> cosmos
    cosmos >> Edge(color="darkred") >> apim
    cosmos >> Edge(color="darkblue") >> dbks
    cosmos >> Edge(color="darkblue") >> functions
    functions >> Edge(color="darkbrown") >> notifyhub

CONSTRUCT OF AZURE DEVOPS PIPELINE TO EXECUTE PYTHON CODE TO CREATE ARCHITECTURE DIAGRAM:-
1. Generate Solution Architecture Diagram using Diagrams, Python and Azure Devops.
2. Commit the Solution Architecture Diagram created to GIT repository.
3. The Pipeline has 2 stages.
4(a). Stage #1 performs below:-
4(b). Install Requisites in the build agent.
4(c). Generate Solution Architecture diagram.
4(d). Copy Generated Solution Architecture diagram to Artifacts staging directory.
4(e). Publish Generated Solution Architecture diagram as Artifacts.
5(i). Stage #2 performs below:-
5(ii). Download Artifacts.
5(iii). Commit Generated Solution Architecture diagram to Azure Devops GIT repository.
5(iv). System Access Token is configured to run the build.

PIPELINE CODE SNIPPET:-

AZURE DEVOPS YAML PIPELINE (azure-pipelines-diagram-as-code-v1.0.yml):-

####################################
# Automation Scope:-
#####################
# 1. Generate Diagrams by Code.
# 2. Commit 2 Git.
####################################

################################################################################################################################
# Important to Note:-
#####################
# 1. The Consumers only need to change the value which are commented in the "Declare Variables" Section.
# 2. If you are changing the value of "pythonCode" Variable, then make sure, you change the value of "DiagramName" Variable. 
################################################################################################################################

trigger:
  none

#######################
# Declare Variables:-
#######################
variables:
  ServiceConnection: 'amcloud-cicd-service-connection' # Please replace with your Service Connection!
  BuildAgent: 'windows-latest' # Please replace with your Build Agent. You can continue to use this as this is Microsoft Hosted Windows Build Agent!
  envName: 'NonProd' # Please replace with your Azure Devops Environment Name
  pythonCode: 'Generate-Gaming-Arch-Diagrams.py' # Please replace with your script name kept in the "Code" Directory! 
  RootWorkingFolderName: 'Digram-As-Code-With-Devops' # Please replace with your Root Working Folder Name!
  ChildWorkingFolderName1: 'Code' # Please replace with your Child Working Folder Name!
  ChildWorkingFolderName2: 'Diagrams' # Please replace with your Child Working Folder Name!
  WorkingDir: '$(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)' 
  TargetFolderName: 'AMDaC' # Please replace with your naming convention!
  Target: '$(build.artifactstagingdirectory)\$(TargetFolderName)'
  Artifact: 'DaC' # Please replace with your naming convention!
  DiagramName: 'Gaming_Architecture.png' # Please replace with the name, you have mentioned inside your Python Script!
  DevopsOrgName: 'ArindamMitra0251' # Please replace with your Azure Devops Organisation Name!
  DevopsPrjName: 'AMCLOUD' # Please replace with your Azure Devops Project Name!
  DevopsRepoName: 'YAML-v1.0' # Please replace with your Azure Devops Repository Name!
  DevOpsGITUser: 'AM' # Please replace with your Custom GIT Username!
  DevOpsGITEmail: 'arindam0310018@gmail.com' # Please replace with your GIT user email address!

######################
# Declare Build Agent:-
######################
pool:
  vmImage: '$(BuildAgent)'

#############################
# Declare Stages:-
# Generate Diagrams by Code
#############################
stages:

- stage: Diagram_As_Code
  jobs:
  - job: Diagram_As_Code
    displayName: Diagram As Code
    steps:
    - task: AzureCLI@2
      displayName: Diagram As Code
      inputs:
        azureSubscription: $(ServiceConnection)
        scriptType: ps
        scriptLocation: inlineScript
        inlineScript: |
          echo "##########################################################"
          $choco_ver = choco -v
          echo "The latest chocolatey version installed is: $choco_ver"
          echo "##########################################################"
          python --version
          echo "#######################################"
          pip --version
          echo "#######################################"
          echo "Installing Graphiz...!"
          echo "#######################################"
          choco install graphviz -y
          echo "#######################################"
          echo "Validate graphviz Installation..."
          echo "########################################"
          sleep 10
          dot -V
          echo "########################################"
          pip install diagrams
          echo "########################################"
          cd $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\
          dir
          echo "########################################"
          python $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\$(pythonCode)   
          cd $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\
          dir
          $outputPath = "$(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName1)\$(DiagramName)"
          if (Test-Path $outputPath) {
             Write-Host "$(DiagramName) created successfully."
             } 
          else {
                Write-Host "$(DiagramName) was NOT created."
                exit 1
                }
          echo "########################################"

###############################################
# Copy Files to Artifacts Staging Directory:-
###############################################
    - task: CopyFiles@2
      displayName: Copy Files Artifacts Staging Directory
      inputs:
        SourceFolder: '$(workingDir)'
        Contents: |
          **/*.png
        TargetFolder: '$(Target)'

# ########################
# # Publish Artifacts:-
# ########################
    - task: PublishBuildArtifacts@1
      displayName: Publish Artifacts
      inputs:
        targetPath: '$(Target)'
        artifactName: '$(Artifact)'     

#############################
# Stage: Commit 2 Code
#############################

- stage: Commit_2_Git
  condition: succeeded('Diagram_As_Code')
  jobs:
  - deployment: 
    displayName: Commit_2_Git
    environment: $(envName)
    pool:
      vmImage: '$(BuildAgent)'
    strategy:
      runOnce:
        deploy:
          steps:
          - checkout: self 
            persistCredentials: true

#########################
# Download Artifacts:-
#########################
          - task: DownloadBuildArtifacts@0
            displayName: Download Artifacts
            inputs:
              buildType: 'current'
              downloadType: 'single'
              artifactName: '$(Artifact)'
              downloadPath: '$(System.ArtifactsDirectory)'

#########################################
# Commit 2 Git:-
# Authentication - System Access Token
#########################################
          - task: PowerShell@2
            displayName: GIT Commit 
            inputs:
              targetType: 'inline'
              script: |
                cd $(System.DefaultWorkingDirectory)\$(RootWorkingFolderName)\$(ChildWorkingFolderName2)
                cp $(System.ArtifactsDirectory)\$(Artifact)\$(TargetFolderName)\$(DiagramName) . 
                echo "#####################"
                echo "Diagram copied!"
                echo "Listing the contents in the current directory:-"
                dir
                echo "#####################"
                git remote -v
                echo "#####################"
                git remote set-url origin https://$(System.AccessToken)@dev.azure.com/$(DevopsOrgName)/$(DevopsPrjName)/_git/$(DevopsRepoName)
                echo "#####################"
                git ls-remote origin
                echo "#####################"
                git config --global user.email "$(DevOpsGITEmail)"
                git config --global user.name "$(DevOpsGITUser)"
                git config --global --unset https.proxy
                git checkout -b $(Build.SourceBranchName)
                git add .
                git commit -m "Output Architecture Diagram"
                git push origin $(Build.SourceBranchName)
            env:
              SYSTEM_ACCESSTOKEN: $(System.AccessToken)

IMPORTANT TO NOTE:-
1. The users only need to change the value which are commented in the "Declare Variables" Section.
2. If you are changing the value of "pythonCode" Variable, then make sure, you change the value of "DiagramName" Variable.

OUTPUT OF EXAMPLE #2:-
1. Configure System Access Token.

2. Successful Pipeline run.

3. Generated Solutions Architecture Diagram as Artifacts Uploaded in Azure Devops.


4. Solutions Architecture Diagram Generated is Committed in Azure Devops Repo.

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Executive and Employee Leadership Framework Applied in my Cloud Team

Arindam Mitra — Sat, 12 Oct 2024 20:40:41 +0000

Greetings to my fellow Technology Advocates and Specialists.

Very recently, my company organized leadership training where we were introduced to a concept followed by an exercise of “Executive and Employee leadership framework.”

VENUE:-

CODE REPOSITORY:-

arindam0310018 / 12-Oct-Tutorial__Executive-and-Employee-Leadership-Framework

Executive and Employee Leadership Framework Applied in my Cloud Team

Executive and Employee Leadership Framework Applied in my Cloud Team:-

Greetings to my fellow Technology Advocates and Specialists.

Very recently, my company organized leadership training where we were introduced to a concept followed by an exercise of “Executive and Employee leadership framework.”

VENUE:-

DEFINITION:-
To better understand this blogpost, the following definition will be useful.
Executive: Any leader (Managing Director, Department Head, Team Lead, …).
Employee: Reporting to a leader.

CONCEPT:-
1. In this exercise, all leaders were organized into groups of five. The purpose was for each person to take turns acting as the Executive for the others. When not in the Executive role, each member would assume the role of an employee.
2. Each group member was assigned a scripted situation and character, which they were expected to portray. The script was identical for everyone, so all participants were aware of each other’s character and situation, providing a

…

View on GitHub

DEFINITION:-
To better understand this blogpost, the following definition will be useful.
Executive: Any leader (Managing Director, Department Head, Team Lead, …).
Employee: Reporting to a leader.

CONCEPT:-
1. In this exercise, all leaders were organized into groups of five. The purpose was for each person to take turns acting as the Executive for the others. When not in the Executive role, each member would assume the role of an employee.
2. Each group member was assigned a scripted situation and character, which they were expected to portray. The script was identical for everyone, so all participants were aware of each other’s character and situation, providing a fair opportunity to prepare for their turn as the Executive.
3. As the executive, you will invite each group member, acting as an employee, into the room one at a time. Each employee will present their scripted concerns, and your task is to offer potential solutions that are acceptable to them, all within a 5-minute timeframe.
4. At the end of the exercise, the group gathers to conduct a retrospective, reflecting on each member’s experience as an executive.

TAKE AWAY(S):-
This exercise showed everyone in the group that employees often have numerous opinions about executives; until they step into an executive role themselves and realize the time and effort required to consider everyone’s viewpoints and develop responses that can be applicable for all. Once promoted, an employee no longer be an individual contributor, making the role quite challenging.

HOW I IMPLEMENTED MY TAKE AWAY(S):-
1. In my cloud platform team, we focus heavily on two main areas:-
(a.) Developing, enhancing, and supporting Cloud Products and Governance.
(b.) Delivering Cloud Projects. In both areas, daily discussions are abundant, and, like any team, we encounter a wide range of opinions on each topic.
2. For Cloud Project Deliveries, this concept doesn’t fully apply since projects often involve just one or two engineers, drawing conclusion easier to achieve.
3. However, when it comes to building, enhancing, and supporting Cloud Products and Governance, reaching a common understanding is more challenging. This is where I implemented this concept:-
(a.) We are currently developing four Cloud Products and two Consulting Services.
(b.) Each platform engineer in the team serves as an executive for one Product or Consulting Service and acts as an employee for the others.
(c.) This approach helps engineers build skills in delegation, collaboration, constructive participation, offering actionable insights, effective communication, and, most importantly, empathy toward their teammates. Without this practice, they may encounter similar challenges when they take on the executive role in a different product or service.

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Tactiq - ChatGPT Meeting Summary

Arindam Mitra — Fri, 16 Aug 2024 23:09:02 +0000

Greetings my fellow Technology Advocates and Specialists.

This is the Chapter #6 of my Data & AI Series based on my recent learning.

In this Session, I will share my recent learning about a tool named Tactiq - ChatGPT Meeting Summary.

ADDITIONAL CONTRIBUTOR(S):-
Tanushri Nayak

CODE REPOSITORY:-

arindam0310018 / 09-May-2024-Data-And-AI__All-In-One

DATA & AI

Data And AI with Azure - All in One:-

Greetings to my fellow Technology Advocates and Specialists.

The Objective of this series is to learn as much as possible on Data and AI and in the process help others.

DATE	TOPICS	CONTENT
09.05.2024	Recap: Microsoft Build AI Day Switzerland 2024	https://dev.to/arindam0310018/recap-microsoft-build-ai-day-switzerland-2024-2b62
12.05.2024	Microsoft OpenAI Architecture	https://dev.to/arindam0310018/microsoft-openai-architecture-2i35
12.05.2024	Microsoft OpenAI Security	https://dev.to/arindam0310018/microsoft-openai-security-5ej6
12.05.2024	Readiness of Organisation for AI Adoption	https://dev.to/arindam0310018/readiness-of-organisation-for-ai-adoption-4eli
12.05.2024	Microsoft OpenAI: Errors I Learned	https://dev.to/arindam0310018/microsoft-openai-errors-i-learned-f4k
17.08.2024	Tactiq - ChatGPT Meeting Summary	https://dev.to/arindam0310018/tactiq-chatgpt-meeting-summary-2942
27.12.2024	OpenAI Operational Status	https://dev.to/arindam0310018/openai-operational-status-4afh

View on GitHub

WHAT IS TACTIQ ?
1. Helps you focus on meeting while AI handles Notes.
2. No More Meeting Notes Manually.
3. Get more out of the meetings with insightful AI Summaries.

TACTIQ URL	https://tactiq.io/

Below follows the steps as how to enable Tactiq Extension in Chrome.

TACTIQ CHROME EXTENSION	https://chromewebstore.google.com/detail/tactiq-chatgpt-meeting-su/fggkaccpbmombhnjkjokndojfgagejfb?utm_source=tactiq-website

ADD TO CHROME:-

CHOOSE YOUR MEETING APP:-

MORE INFORMATION:-
1. One enabled in Chrome, it will provide you an interface to associate your email address.
2. Next time, when you are in a meeting using Teams, Google Meet or Zoom, Tactics Interface will open automatically and you can see the live recording of in-meeting transcriptions and insightful AI summaries.
3. Once Meeting ends, it will provide you option to export in PDF, among other things.

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Code Generated Architecture Diagram

Arindam Mitra — Thu, 15 Aug 2024 20:23:52 +0000

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate How to Create Azure Solutions Architecture Diagram by Code.

I had the Privilege to talk on this topic in ONE Azure Community:-

NAME OF THE AZURE COMMUNITY	TYPE OF SPEAKER SESSION
Festive Tech Calendar - 2024	Virtual

EVENT ANNOUNCEMENTS:-

VIRTUAL SESSION:-
LIVE DEMO was Recorded as part of my Presentation in FESTIVE TECH CALENDAR - 2024 Forum/Platform
Duration of My Demo = 49 Mins 02 Secs

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Example #1: Create "Basic Azure App Service Architecture Diagram" by Code.
2.	Example #2: Create "Gaming Architecture Diagram" by Code.

PRE-REQUISITES:-
1. Python 3.6 or higher.
2. Graphviz
3. pip

VALIDATE PRE-REQUISITES:-

COMMANDS TO VERIFY:-

python --version
dot -V
pip --version

INSTALL DIAGRAMS:-

Install "diagrams" using "pip":-

pip install diagrams

CODE REPOSITORY:-

arindam0310018 / 31-July-2024-DevOps__Diagram-As-Code

DIAGRAM AS CODE

Diagram As Code:-

Greetings to my fellow Technology Advocates and Specialists.

This is "Diagram As Code" Series !

DATE	TOPICS	CONTENT
01.08.2024	Visualizing Cloud Designations with Mermaid	https://dev.to/arindam0310018/visualizing-cloud-designations-with-mermaid-3bl
15.08.2024	Code Generated Architecture Diagram	https://dev.to/arindam0310018/code-generated-architecture-diagram-13o3
19.11.2024	Code Generated Architecture Diagram using Devops	https://dev.to/arindam0310018/code-generated-architecture-diagram-using-azure-devops-2ah4

I had the Privilege to talk on this topic in ONE Azure Communities:-

NAME OF THE AZURE COMMUNITY	TYPE OF SPEAKER SESSION
Festive Tech Calendar - 2024	Virtual

EVENT ANNOUNCEMENTS:-

View on GitHub

REFERENCE LINKS:-
1. Diagram as Code
2. Diagram as Code - Installation
3. Diagram as Code - Examples
4. Diagram as Code - List of Azure Providers

CONCEPTS:-

I.) DIAGRAMS:-
1. Represents a global diagram context.
2. Diagram context can be created with Diagram class.
3. The first parameter of Diagram constructor will be used for output filename.

II.) NODES:-
1. Represents a single system component object.
2. A node object consists of three parts: i) Provider, ii) Resource type and iii) Name.

III.) CLUSTERS:-
1. Allows you group (or clustering) the nodes.

IV.) EDGES:-
1. Represents a connection between Nodes with some additional properties.

Now, we proceed in Creating Architecture Diagram using Diagrams and Python.

CONSTRUCT OF THE PYTHON CODE TO CREATE ARCHITECTURE DIAGRAM:-
1. Import Diagram, Cluster and Edge.
2. Import the Provider Icons for creating diagrams.
3. Creating the building blocks using Nodes and Cluster.
4. Connect the building blocks using Edges.

EXAMPLE #1:

Create "Basic Azure App Service Architecture Diagram" by Code.

Below follows the Python Code (Generate-Basic-Azure-App-service-Arch-Diagram.py):-

############################################################
## Architecture Diagram: Basic Azure App Service:-

## Components include:-
# 1. User
# 2. Azure Entra ID
# 3. Azure Monitor
# 4. Azure Application Insights
# 5. Azure User Assigned Managed Identity
# 6. Azure Key Vault 
# 7. Azure App Services
# 8. Azure SQL Servers

############################################################

######################################################
# Import Diagram, Cluster and Edge.
# Import the Provider Icons for creating diagrams.
######################################################

from diagrams import Cluster, Diagram, Edge
from diagrams.azure.general import Helpsupport, Servicehealth
from diagrams.azure.devops import ApplicationInsights
from diagrams.azure.security import KeyVaults
from diagrams.azure.identity import ManagedIdentities, ActiveDirectory
from diagrams.azure.compute import AppServices
from diagrams.azure.database import SQLServers

#########################################################
# Creating the building blocks using Nodes and Cluster.
#########################################################

with Diagram("Basic Azure App Service Architecture", show=False, direction="TB"):
    usr = Helpsupport("User")

    with Cluster("Compute"):
        components_webapp = [AppServices("AppServices"), KeyVaults("KV"), ManagedIdentities("UMID")]

    with Cluster("Data"):
        components_db = SQLServers("Azure SQL Database")

    with Cluster("Identity"):
        components_identity = [ActiveDirectory("Microsoft Entra ID")]

    with Cluster("Monitoring"):
        components_monitor = [ApplicationInsights("App Insights"), Servicehealth("Azure Monitor")]

############################################
# Connect the building blocks using Edges.
############################################

    usr >> Edge(color="darkorange") >> components_webapp

    components_webapp >> Edge(color="darkgreen") >> components_db

EXECUTE THE PYTHON CODE:-

python.exe .\Generate-Basic-Azure-App-service-Arch-Diagram.py

OUTPUT OF EXAMPLE #1:-

EXAMPLE #2:

Create "Gaming Architecture Diagram" by Code.

Below follows the Python Code (Generate-Gaming-Arch-Diagrams.py):-

############################################################
## Architecture Diagram: Gaming using Azure Cosmos DB:-

## Components include:-
# 1. User
# 2. Azure Traffic Manager
# 3. Azure Content Delivery Network
# 4. Azure Storage
# 5. Azure API Management 
# 6. Azure Cosmos DB
# 7. Azure Databricks
# 8. Azure Functions
# 9. Azure Notification Hubs

############################################################

######################################################
# Import Diagram, Cluster and Edge.
# Import the Provider Icons for creating diagrams.
######################################################

from diagrams import Cluster, Diagram, Edge
from diagrams.azure.general import Helpsupport
from diagrams.azure.network import TrafficManagerProfiles, CDNProfiles
from diagrams.azure.storage import StorageAccounts
from diagrams.azure.integration import APIManagement
from diagrams.azure.database import CosmosDb
from diagrams.azure.analytics import Databricks
from diagrams.azure.compute import FunctionApps
from diagrams.azure.mobile import NotificationHubs

#########################################################
# Creating the building blocks using Nodes and Cluster.
#########################################################

# with Diagram("GAMING ARCHITECTURE", show=False, direction="TB"):
with Diagram("GAMING ARCHITECTURE", show=False):
    usr = Helpsupport("User")

    # atm = TrafficManagerProfiles("Azure Traffic Manager")

    apim = APIManagement("Azure API Apps")

    cosmos = CosmosDb("Azure Cosmos DB")

    dbks = Databricks("Azure Databricks")

    # cdn = CDNProfiles ("Azure CDN")

    # storage = StorageAccounts("Azure Storage (Media Files)")

    functions = FunctionApps("Azure Functions")

    notifyhub = NotificationHubs("Azure Notification Hubs")

    with Cluster(""):
         atm = TrafficManagerProfiles("Traffic Manager")

    with Cluster(""):
         cdn = CDNProfiles ("Azure CDN")

    with Cluster(""):
         storage = StorageAccounts("Azure Storage")

############################################
# Connect the building blocks using Edges.
############################################

    usr >> Edge(color="darkgreen") >> atm
    cdn >> Edge(color="darkblue") >> atm
    storage >> Edge(color="darkpurple") >> cdn
    atm >> Edge(color="darkorange") >> apim
    apim >> Edge(color="darkred") >> cosmos
    cosmos >> Edge(color="darkred") >> apim
    cosmos >> Edge(color="darkblue") >> dbks
    cosmos >> Edge(color="darkblue") >> functions
    functions >> Edge(color="darkbrown") >> notifyhub

EXECUTE THE PYTHON CODE:-

python.exe .\Generate-Gaming-Arch-Diagrams.py

OUTPUT OF EXAMPLE #2:-

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Visualizing Cloud Designations with Mermaid

Arindam Mitra — Wed, 31 Jul 2024 23:11:04 +0000

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate How to Create FlowChart Using Mermaid: A Step-by-Step Guide with Cloud Designations as Example.

I had the Privilege to talk on this topic in ONE Azure Community:-

NAME OF THE AZURE COMMUNITY	TYPE OF SPEAKER SESSION
Festive Tech Calendar - 2024	Virtual

EVENT ANNOUNCEMENTS:-

VIRTUAL SESSION:-
LIVE DEMO was Recorded as part of my Presentation in FESTIVE TECH CALENDAR - 2024 Forum/Platform
Duration of My Demo = 49 Mins 02 Secs

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Create FlowChart.
2.	Create FlowChart using Subgraph.

REQUIREMENTS:-
1. Mermaid Live Editor

CODE REPOSITORY:-

arindam0310018 / 31-July-2024-DevOps__Diagram-As-Code

DIAGRAM AS CODE

Diagram As Code:-

Greetings to my fellow Technology Advocates and Specialists.

This is "Diagram As Code" Series !

DATE	TOPICS	CONTENT
01.08.2024	Visualizing Cloud Designations with Mermaid	https://dev.to/arindam0310018/visualizing-cloud-designations-with-mermaid-3bl
15.08.2024	Code Generated Architecture Diagram	https://dev.to/arindam0310018/code-generated-architecture-diagram-13o3
19.11.2024	Code Generated Architecture Diagram using Devops	https://dev.to/arindam0310018/code-generated-architecture-diagram-using-azure-devops-2ah4

I had the Privilege to talk on this topic in ONE Azure Communities:-

NAME OF THE AZURE COMMUNITY	TYPE OF SPEAKER SESSION
Festive Tech Calendar - 2024	Virtual

EVENT ANNOUNCEMENTS:-

View on GitHub

REFERENCE LINKS:-
1. Overall Mermaid Documentation
2. Mermaid FlowChart Basic Syntax

WHAT IS MERMAID ?
1. Mermaid lets you create diagrams and visualizations using text and code.
2. It is based on JavaScript and inspired from Markdown Text.

NOTE:-
If users have familiarity or a working experience with Markdown, then understanding Mermaid Syntax comes easy.

MERMAID FLOWCHART: POINTS TO NOTE:-
1. Flowcharts are composed of nodes (geometric shapes) and edges (arrows or lines).
Possible FlowChart orientations are: a.) TB - Top to bottom; b.) TD - Top-down/ same as top to bottom; c.) BT - Bottom to top; d.) RL - Right to left; LR - Left to right.

USECASE #1:-
Create FlowChart.

Below follows the code:-

flowchart BT
    B(Chief Cloud Officer) --> A(Chief Technology Officer)
    C(Cloud Architect) --> B
    D(Cloud Service Manager) --> B
    E(Cloud Application Lead) --> B
    C1(Devops Engineer) --> C
    C2(IaC Developer) --> C1
    C3(IaC Operations Engineer) --> C2
    F(Support Engineer) --> C3
    D1(Cloud Operations Manager) --> D
    D2(Cloud Operations Engineer) --> D1
    F(Support Engineer) --> D2
    E1(Cloud Developer) --> E

EXPLANATION OF USECASE #1 MERMAID FLOWCHART CODE:-
1. `flowchart BT` - This Syntax indicates that the orientation of the FlowChart will be Bottom to Top.
2. `B(Chief Cloud Officer)` - This Syntax indicates a node with round edges.
3. `-->` - This Syntax indicates a link with arrow head.

OUTPUT FOR USECASE #1:-

USECASE #2:-
Create FlowChart using Subgraph.

Below follows the code:-

flowchart BT
    B(Chief Cloud Officer) --> A(Chief Technology Officer)
    C(Cloud Architect) --> B
    subgraph PLATFORM
    C1(Devops Engineer) --> C
    C2(IaC Developer) --> C1
    C3(IaC Operations Engineer) --> C2
    end
    D(Cloud Service Manager) --> B
    subgraph OPERATIONS
    D1(Cloud Operations Manager) --> D
    D2(Cloud Operations Engineer) --> D1
    end
    E(Cloud Application Lead) --> B
    subgraph APPLICATION
    E1(Cloud Developer) --> E    
    end
    subgraph SUPPORT
    F(Support Engineer) --> C3
    F(Support Engineer) --> D2
    end

EXPLANATION OF USECASE #2 MERMAID FLOWCHART CODE:-
1. `flowchart BT` - This Syntax indicates that the orientation of the FlowChart will be Bottom to Top.
2. `B(Chief Cloud Officer)` - This Syntax indicates a node with round edges.
3. `-->` - This Syntax indicates a link with arrow head.
4. `subgraph PLATFORM` or `subgraph OPERATIONS` or `subgraph SUPPORT` - This Syntax indicates grouping of nodes in a grid and providing a title to it.

SYNTAX OF "SUBGRAPH":-

subgraph one
    a1-->a2
    end

where,

"subgraph one" - Title of the Grid.
"a1-->a2" - a1 and a2 are nodes linked with arrow head.
"end" - End of the Grid.

OUTPUT FOR USECASE #2:-

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Boosting Devops Productivity with Forms and Power Automate

Arindam Mitra — Mon, 29 Jul 2024 22:33:07 +0000

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate How to create Azure Devops Work-Items using Microsoft Forms and Power Automate.

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Create Microsoft Forms and Publish.
2.	Create Power Automate Flow - Automated Cloud Flow.
3.	Integrate Microsoft Forms and Azure Devops with Power Automate.
4.	There are 3 Actions created in the Automated Cloud Flow.
4(a).	Action#1: When a New Response is Submitted.
4(b).	Action#2: Get Response Details.
4(c).	Action#3: Create a Work-item in Azure Devops.
5.	Create Azure Devops Work-items by submitting Microsoft Forms.

REQUIREMENTS:-

Access to Microsoft Forms.
Access to Microsoft Power Automate.
Azure DevOps Organisation and Project.

CODE REPOSITORY:-

arindam0310018 / 30-July-2024-DevOps__Boosting-Devops-Productivity-with-Forms-and-Power-Automate

Boosting Devops Productivity with Forms and Power Automate

Boosting Devops Productivity with Forms and Power Automate:-

Greetings to my fellow Technology Advocates and Specialists.

In this Session, I will demonstrate How to create Azure Devops Work-Items using Microsoft Forms and Power Automate.

AUTOMATION OBJECTIVES:-

#	TOPICS
1.	Create Microsoft Forms and Publish.
2.	Create Power Automate Flow - Automated Cloud Flow.
3.	Integrate Microsoft Forms and Azure Devops with Power Automate.
4.	There are 3 Actions created in the Automated Cloud Flow.
4(a).	Action#1: When a New Response is Submitted.
4(b).	Action#2: Get Response Details.
4(c).	Action#3: Create a Work-item in Azure Devops.
5.	Create Azure Devops Work-items by submitting Microsoft Forms.

REQUIREMENTS:-

Access to Microsoft Forms.
Access to Microsoft Power Automate.
Azure DevOps Organisation and Project.

Below follows the step by step Process:-

1. Create Microsoft Forms and Publish.
a. Login to Microsoft Forms and Click on "New Form".

b.

…

View on GitHub

Below follows the step by step Process:-

1. Create Microsoft Forms and Publish.
a. Login to Microsoft Forms and Click on "New Form".

b. Create the Required Microsoft Form.

c. Once Microsoft Form is created, Click on "Preview".


d. Then click on "Present".



From above, copy the link under the QR Code and open in another browser tab.

2. Create Power Automate Flow.
a. Login to Microsoft Power Automate > Create > Automated cloud flow.

b. Provide the Flow Name, Choose the below Trigger and Click on "Create".

3. Integrate Microsoft Forms with Power Automate.

4. There are 3 Actions created in the Automated Cloud Flow.
4(a) Action#1: When a New Response is Submitted.

Add an Action - Microsoft Forms

4(b) Action#2: Get Response Details.


When a new response is submitted using Microsoft Forms, Response ID is captured by selecting "Dynamic Content".



4(c) Action#3: Create a Work-item in Azure Devops.

Ensure the "Work Item Type" is selected as "Issue".

The "Title" option in "Create a Work Item" Action in Microsoft Power Automate is mapped to Microsoft Forms "Get Response Details" "Task Name" under "Dynamic Content".


The "Description" option in "Create a Work Item" Action in Microsoft Power Automate is mapped to Microsoft Forms "Get Response Details" "Description" under "Dynamic Content".

5. Create Azure Devops Work-items by submitting Microsoft Forms.

Response was submitted.

Azure Devops Work item was successfully created.

The Success Status can also be viewed from Microsoft Power Automate.

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge

Microsoft OpenAI: Errors I Learned

Arindam Mitra — Sun, 12 May 2024 20:01:42 +0000

Greetings my fellow Technology Advocates and Specialists.

This is the Chapter #5 of my Data & AI Series based on Microsoft Build AI Day, Switzerland, 2024.

In this Session, I will provide readers, the list of Known Errors in Microsoft OpenAI. which I learned recently in AI Day, Switzerland.

CODE REPOSITORY:-

arindam0310018 / 09-May-2024-Data-And-AI__All-In-One

DATA & AI

Data And AI with Azure - All in One:-

Greetings to my fellow Technology Advocates and Specialists.

The Objective of this series is to learn as much as possible on Data and AI and in the process help others.

DATE	TOPICS	CONTENT
09.05.2024	Recap: Microsoft Build AI Day Switzerland 2024	https://dev.to/arindam0310018/recap-microsoft-build-ai-day-switzerland-2024-2b62
12.05.2024	Microsoft OpenAI Architecture	https://dev.to/arindam0310018/microsoft-openai-architecture-2i35
12.05.2024	Microsoft OpenAI Security	https://dev.to/arindam0310018/microsoft-openai-security-5ej6
12.05.2024	Readiness of Organisation for AI Adoption	https://dev.to/arindam0310018/readiness-of-organisation-for-ai-adoption-4eli
12.05.2024	Microsoft OpenAI: Errors I Learned	https://dev.to/arindam0310018/microsoft-openai-errors-i-learned-f4k
17.08.2024	Tactiq - ChatGPT Meeting Summary	https://dev.to/arindam0310018/tactiq-chatgpt-meeting-summary-2942
27.12.2024	OpenAI Operational Status	https://dev.to/arindam0310018/openai-operational-status-4afh

View on GitHub

Error #1:-
HTTP Code 429
This means "Too many requests exceeding resource limits". The limitation can be because of CPU usage, Memory usage and maximum concurrent connections.

Error #2:-
Common Error with GPT 3.5

I will keep updating this blog as and when I learn more !

Hope You Enjoyed the Session!!!

Stay Safe | Keep Learning | Spread Knowledge