Skip to content

Latest commit

 

History

History
86 lines (48 loc) · 4.38 KB

File metadata and controls

86 lines (48 loc) · 4.38 KB

Challenge 00 - Preparing your Development Environment

Home - Next Challenge>

Introduction

A cloud engineer should have the right set of tools in order to be successful in deploying an integration solution in Azure.

Description

In this challenge we will be setting up all the tools needed to complete our challenges.

Azure Subscription

You will need an Azure subscription to complete this hackathon. If you don't have one, sign up for a free Azure subscription by clicking this link.

If you are using Azure for the first time, this subscription comes with:

  • $200 free credits for use for up to 30 days
  • 12 months of popular free services (includes API Management, Azure Functions, Virtual Machines, etc.)
  • Then there are services that are free up to a certain quota

Details can be found here on free services.

If you have used Azure before, we will still try to limit cost of services by suspending, shutting down services, or destroy services before the end of the hackathon. You will still be able to use the free services up to their quotas.

Azure CLI

You also need to make sure that you have installed the latest version of Azure CLI. To do so, open Visual Studio Code Terminal window and run az upgrade.

This hack requires version 2.20.0 or higher.

Visual Studio Code and Bicep extension

You will need to set-up your environment using Visual Studio Code with Bicep extension to develop and deploy Azure resources using Bicep files. See Install Bicep tools for installation details.

This hack requires VS Code version 1.63 or higher.

Set default Azure subscription and resource group

You can set your default Azure subscription and resource group by:

  • Sign-in by running az login in the VS Code Terminal
  • Set default subscription by running az account set --subscription "<subscription name or subscription id>"
  • Create a resource group by running az group create -l <location> -n <resource group name>
  • Then, set the resource group as default by running az configure --defaults group=<resource group name>

Managing Cloud Resources

We can manage cloud resources via the following ways:

Azure Portal

Manage your resources via a web interface (i.e. GUI) at https://portal.azure.com/

The Azure Portal is a great tool for quick prototyping, proof of concepts, and testing things out in Azure by deploying resources manually. However, when deploying production resources to Azure, it is highly recommended that you use an automation tool, templates, or scripts instead of the portal.

Azure Cloud Shell

Build, manage, and monitor everything from simple web apps to complex cloud applications in a single, unified console via the Azure Cloud Shell.

Azure DevOps or GitHub

You can create an Azure DevOps project to use Azure Pipelines for CI/CD. If you prefer to use GitHub Actions instead, you must create a new GitHub repository.

Postman

Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster. Sign up for free to get started with Postman.

Back to Top