stack-spot / stackspot-studio-data-roadmap

Repositorio para equipe de criacao de conteudo para poder criar as issues de repositorio
https://stackspot.com
Apache License 2.0
0 stars 0 forks source link

[DM] H3 - Atualizar versão do provider Terraform #188

Closed danielmaionzup closed 9 months ago

danielmaionzup commented 9 months ago

Erro na governança federada executando plan na versão 5.35.0

- Installing hashicorp/aws v5.35.0...
- Installed hashicorp/aws v5.35.0 (signed by HashiCorp)
- Using previously-installed hashicorp/archive v2.4.2

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
╷
│ Error: Unsupported argument
│
│   on .terraform\modules\federated_s3_data_storage\main.tf line 74, in data "aws_iam_policy_document" "aggregated_iam_policy_document":
│   74:   source_json   = var.s3_bucket.policy
│
│ An argument named "source_json" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on .terraform\modules\federated_s3_data_storage\main.tf line 75, in data "aws_iam_policy_document" "aggregated_iam_policy_document":
│   75:   override_json = data.aws_iam_policy_document.s3_iam_policy_document.json
│
│ An argument named "override_json" is not expected here.
danielmaionzup commented 9 months ago

Warning Governança Federada

╷
│ Warning: Argument is deprecated
│
│   with module.federated_s3_data_storage.aws_s3_bucket.this_s3_bucket,
│   on .terraform\modules\federated_s3_data_storage\main.tf line 1, in resource "aws_s3_bucket" "this_s3_bucket":
│    1: resource "aws_s3_bucket" "this_s3_bucket" {
│
│ Use the aws_s3_bucket_server_side_encryption_configuration resource instead
│
│ (and 2 more similar warnings elsewhere)
╵