Terraform Workflow with Azure: Write, Plan and Apply

Поделиться
HTML-код
  • Опубликовано: 15 окт 2024

Комментарии • 21

  • @PawanKumar-b8l8x
    @PawanKumar-b8l8x Месяц назад

    Awesome.... I just started Terraform and this video explained it very well. Thank you so much Travis 👏👏👏

  • @JodyWheat
    @JodyWheat Год назад +3

    I didn't know how to get started until I watched this video. It is exactly what I needed!

  • @alwinm5179
    @alwinm5179 3 месяца назад

    Awesome Video. This the video I tried to find for a while and finally found it. Thanks for making this.

  • @soumztelugu
    @soumztelugu Год назад

    No one can explain like you Travis! Thanku so much

  • @lucasspencer1847
    @lucasspencer1847 2 года назад

    Travis you're an absolute wizard! I needed this video.
    Thank you!

  • @tahmeedhossain2910
    @tahmeedhossain2910 Год назад

    Exactly what I was looking for. Thank you so much for this.

  • @YiannosG
    @YiannosG 2 года назад

    Thanks for both these videos, much appreciated.

  • @MinFel
    @MinFel 2 года назад +1

    Great video, thank you very much.

    • @Ciraltos
      @Ciraltos  2 года назад

      You are welcome!

  • @weixing4520
    @weixing4520 2 года назад

    Excellent !! Thank you!!

  • @bhavanishankar8300
    @bhavanishankar8300 Год назад

    Really Wonderful!

  • @sayantansaha3427
    @sayantansaha3427 Год назад

    Thanks for the video ,, helped a lot,, just one question , in this video time 6:17 you changed the configuration options with features . Could you please elaborate why we need to do this ? with configuration option I ran and facing error, please explain . thanks in advance

  • @andyhuynh2450
    @andyhuynh2450 2 года назад

    This is such a great video. Is there a way to lock Apply workflow with an approval process in vscode?

  • @kartheek2048
    @kartheek2048 2 года назад

    Thanks man, you helped a lot.

  • @SandeepYatri
    @SandeepYatri 2 года назад

    Thank You for wonderful videos!!

    • @Ciraltos
      @Ciraltos  2 года назад

      Glad you like them!

  • @megaa1c
    @megaa1c 2 года назад

    hi @Travis. are you going to update your zero to hero course with a lesson on how to deploy AVD via terraform and azure devops pipelines ? reckon it might be useful for many who want to automate AVD deployment using custom image build and terraform

    • @makeitcloudy
      @makeitcloudy 2 года назад

      seems there is no point reinventig the wheel where there are examples of doing this on github among the go-euc for example

  • @dhnaveen
    @dhnaveen 2 года назад

    Hi Travis, I get the following error while I reun the az exyension add command
    Unable to get extension index.
    Please ensure you have network connection. Error detail: HTTPSConnectionPool(host='azcliextensionsync.blob.core.windows.net', port=443): Max retries exceeded with url: /index1/index.json (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

  • @adamzachary6947
    @adamzachary6947 2 года назад

    I have a quick question, I'm fairly new to TF.
    I'm building a solution and creating bunch of resource groups and some other resources in each resource group.
    Everything works fine, but now I want to include a azurerm_management_lock to my resource groups.
    It keeps failing on me. with a strange error.
    Error: parsing "resource_group_lock": parsing scope prefix: unable to find the scope prefix from the value "resource_group_lock" with the regex "^((.){1,})/providers/Microsoft.Authorization/locks/(.){1,}"
    My Code
    resource "azurerm_resource_group" "rg" {
    count = var.create_condition == true ?length(var.RG_Name):0
    name = element(var.RG_Name, count.index)
    location = var.RG_Location
    }
    resource "azurerm_management_lock" "rg-level" {
    count = var.create_condition == true ? length(var.RG_Name):0
    name = var.lock_level_name
    scope = azurerm_resource_group.rg[count.index].id
    lock_level = var.lock_level
    }

  • @sidzhang
    @sidzhang 2 года назад

    06:11 why we need to remove this and replace with feature{} ?