The provider doesn't work with the latest version of minio -

[SergeiGorbushinBluescape]

Prerequisites

• I haven't found any similar issues

Description

The provider doesn't work with the latest version of minio

Steps to Reproduce

1. Deploy the latest version of minio - chart 11.10.25, image 2022.12.12-debian-11-r0, clientImage 2022.12.13-debian-11-r0
2. Try to add the first bucket using the minio_s3_bucket resource
3. [and so on...]

Expected behavior: A new bucket has been created

Actual behavior: The provider throws the following errors:

1. The specific bucket doesn't exist;
2. 308 permanent redirect.

Reproduces how often: Always

Versions

The provider version is 1.10.0 The terraform version is 1.1.9 The minio versions are chart 11.10.25, image 2022.12.12-debian-11-r0, clientImage 2022.12.13-debian-11-r0

Additional Information

-

[pjsier]

@SergeiGorbushinBluescape thanks for the report! Are you able to confirm that this does work with earlier versions of minio? I wasn't able to reproduce this by updating this repo's Docker image to be the minio release you're mentioning here

[SergeiGorbushinBluescape]

Hello, No, I haven’t tried it with earlier versions of minio. Have you tried to upgrade the helm chart itself to the latest version?

Kind regards, Sergei Gorbushin

From: Pat Sier @.> Date: Tuesday, January 17, 2023 at 1:02 AM To: aminueza/terraform-provider-minio @.> Cc: Sergei Gorbushin @.>, Mention @.> Subject: Re: [aminueza/terraform-provider-minio] The provider doesn't work with the latest version of minio - (Issue #416)

@SergeiGorbushinBluescapehttps://github.com/SergeiGorbushinBluescape thanks for the report! Are you able to confirm that this does work with earlier versions of minio? I wasn't able to reproduce this by updating this repo's Docker image to be the minio release you're mentioning here

— Reply to this email directly, view it on GitHubhttps://github.com/aminueza/terraform-provider-minio/issues/416#issuecomment-1384682949, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2WPDZPXO3MWF2KUXJZUNJLWSXOPNANCNFSM6AAAAAAT45ZWFE. You are receiving this because you were mentioned.Message ID: @.***>

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

[pjsier]

Not sure I’m following, is this only happening in a Kubernetes helm deployment? I haven’t tested that, but that’s potentially a separate issue if it is working against the latest Docker image

[SergeiGorbushinBluescape]

I have a minio installed in my k8s cluster. I try adding buckets to that instance of minio using terraform:

provider "minio" { minio_server = local.minio_server_api minio_user = var.minio_accessKey != "" ? var.minio_accessKey : random_string.autogenerated_minio_accessKey.result minio_password = var.minio_secretKey != "" ? var.minio_secretKey : random_string.autogenerated_minio_secretKey.result }

resource "minio_s3_bucket" "assets_bucket" { bucket = "assets"

depends_on = [ helm_release.bitnami-minio ] }

resource "minio_ilm_policy" "bucket-lifecycle-rules" { bucket = minio_s3_bucket.assets_bucket.bucket

rule { id = "assets_bucket_rendered_images_expire-1d" filter = "renderedImages/" expiration = "1d" }

depends_on = [ minio_s3_bucket.assets_bucket ] }

resource "minio_s3_bucket" "shared-assets_bucket" { bucket = "shared-assets"

depends_on = [ helm_release.bitnami-minio ] }

and get errors: @.*** or

• 308 permanent redirect At the same lines.

Kind regards, Sergei Gorbushin

From: Pat Sier @.> Date: Friday, January 20, 2023 at 3:10 AM To: aminueza/terraform-provider-minio @.> Cc: Sergei Gorbushin @.>, Mention @.> Subject: Re: [aminueza/terraform-provider-minio] The provider doesn't work with the latest version of minio - (Issue #416)

Not sure I’m following, is this only happening in a Kubernetes helm deployment? I haven’t tested that, but that’s potentially a separate issue if it is working against the latest Docker image

— Reply to this email directly, view it on GitHubhttps://github.com/aminueza/terraform-provider-minio/issues/416#issuecomment-1397840828, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2WPDZNX25FRTYEOWSDUQNDWTHXXXANCNFSM6AAAAAAT45ZWFE. You are receiving this because you were mentioned.Message ID: @.***>

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

[BuJo]

The provider version is 1.10.0
The terraform version is 1.1.9

The terraform version is really old. Only 1.3 onwards is supported, could you test with 1.3.x and provider version >= 1.12.0 that and reopen the issue if it is still happening?