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.

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

[Bug]: aws_transfer_workflow does not save state for copy_step_details #29965

Open
rdbraber opened this issue Mar 13, 2023 · 1 comment
Open
Labels
bug Addresses a defect in current functionality. service/transfer Issues and PRs that pertain to the transfer service.

Comments

@rdbraber
Copy link

rdbraber commented Mar 13, 2023

Terraform Core Version

1.3.3

AWS Provider Version

4.57.1

Affected Resource(s)

aws_transfer_workflow

Expected Behavior

When creating copy_step_details, those steps should be kept in state.

Actual Behavior

The state for the the copy_step_details is empty. Also when trying to import a workflow that was created in the AWS console, which contains copy steps, the copy_step_details are empty.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

// Provider configuration
terraform {
  required_version = "1.3.3"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.57.1"
    }
  }
}

provider "aws" {
  region = "eu-central-1"
}

resource "aws_s3_bucket" "example_bucket" {
  acl = "private"
  versioning {
    enabled = false
  }
  bucket_prefix = "aws-transfer-workflow"
}

resource "aws_transfer_workflow" "example_workflow" {
  description = "example workflow"
  steps {
    copy_step_details {
      name                 = "backup"
      source_file_location = "$${original.file}"
      overwrite_existing   = "TRUE"
      destination_file_location {
        s3_file_location {
          key    = "home/$${transfer:UserName}/$${transfer:UploadDate}/"
          bucket = aws_s3_bucket.example_bucket.id
        }
      }
    }
    type = "COPY"
  }
}

Steps to Reproduce

After running terraform init and terraform apply, the part of the aws_transfer_workflow in the state file looks like:

{
  "version": 4,
  "terraform_version": "1.3.3",
  "serial": 7,
  "lineage": "9377fd64-8301-68cc-5452-569194faf32d",
  "outputs": {},
  "resources": [
    {
      "mode": "managed",
      "type": "aws_transfer_workflow",
      "name": "example_workflow",
      "provider": "provider[\"registry.terraform.io/hashicorp/aws\"]",
      "instances": [
        {
          "schema_version": 0,
          "attributes": {
            "arn": "arn:aws:transfer:eu-central-1:XXXXXXXXXXXX:workflow/w-2ecf891966386c71d",
            "description": "example workflow",
            "id": "w-2ecf891966386c71d",
            "on_exception_steps": [],
            "steps": [
              {
                "copy_step_details": [],
                "custom_step_details": [],
                "delete_step_details": [],
                "tag_step_details": [],
                "type": "COPY"
              }
            ],
            "tags": null,
            "tags_all": {}
          },
          "sensitive_attributes": [],
          "private": "bnVsbA==",
          "dependencies": [
            "aws_s3_bucket.example_bucket"
          ]
        }
      ]
    }
  ],
  "check_results": []
}

When running a terraform plan again it will show changes to the copy_step_details again.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@rdbraber rdbraber added bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Mar 13, 2023
@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added service/s3 Issues and PRs that pertain to the s3 service. service/transfer Issues and PRs that pertain to the transfer service. labels Mar 13, 2023
@justinretzolk justinretzolk removed service/s3 Issues and PRs that pertain to the s3 service. needs-triage Waiting for first response or review from a maintainer. labels Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/transfer Issues and PRs that pertain to the transfer service.
Projects
None yet
Development

No branches or pull requests

2 participants