Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade terraform and aws provider to latest possible #21

Closed
wants to merge 8 commits into from
Closed

Upgrade terraform and aws provider to latest possible #21

wants to merge 8 commits into from

Commits on Sep 29, 2023

  1. Run terraform 0.12upgrade 

    Problem: we'd like to use latest tf version, but the tf state uses 0.11

Solution: go back in time to tf 0.12.29 and apply `terraform 0.12upgrade`

see https://developer.hashicorp.com/terraform/language/v1.1.x/upgrade-guides/0-12
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    3c517aa View commit details
    Browse the repository at this point in the history

  2. Run terraform 0.13upgrade 

    Problem: we'd like to use latest tf version, but the tf state uses 0.12

Solution: go back in time to tf 0.13.7 and apply `terraform 0.13upgrade`

https://developer.hashicorp.com/terraform/language/v1.1.x/upgrade-guides/0-13
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade#domain_validation_options-changed-from-list-to-set

Meanwhile a small change was detected, but following the suggestion
`terraform state mv 'aws_route53_record.cert_validation[0]'
'aws_route53_record.cert_validation["ghc.dev"]'` there was no change
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    ecdb6b1 View commit details
    Browse the repository at this point in the history

  3. Upgrade to tf 0.15 

    Problem: we'd like to use latest tf version, but the tf state uses 0.14

Solution: go back in time to tf 0.15.5, run terraform plan, fix
incompatilbities, terraform apply
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    b5a8e59 View commit details
    Browse the repository at this point in the history

  4. Upgrade aws provider to 3.76 

    Problem: we would like to use the latest version from AWS provider, but
there were some deprecated attributes

Solution: upgrade AWS provider to the latest 3.xx and adjust resources
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    4ad8eb0 View commit details
    Browse the repository at this point in the history

  5. Upgrade AWS provider to 4.67 

    Problem: we would like to use the latest version from AWS provider, but
there were attributes changes during the years

Solution: upgrade AWS provider to the latest 4.xx and adjust resources
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    1b79b68 View commit details
    Browse the repository at this point in the history

  6. Upgrade AWS provider to 5.19 

    Problem: we would like to use the latest version from AWS provider

Solution: upgrade AWS provider to the latest 5.xx
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    9631f47 View commit details
    Browse the repository at this point in the history

  7. Replace nix-shell usage with nix develop

    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    b3c76d6 View commit details
    Browse the repository at this point in the history

  8. Upgrade tf to 1.5.7 

    Problem: we would like to use latest tf version

Solution: update flake nixpkgs and tf version
    @karandit
    karandit committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    93f0302 View commit details
    Browse the repository at this point in the history