Hi, thanks for your provider allowing us to define access & secret keys. I'm having an issue since about one week where I cannot initialize that specific provider as soon as I declare a related resource in my terraform code:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 2.62"
    }
    ...
    }
    minio = {
      source  = "refaktory/minio"
      version = "0.1.0"
    }
  }
}

provider "minio" {
  endpoint = "my-tls-minio-domain.tld"
  access_key = "my_access_key_that_allows_access_to_my_s3_buckets"
  secret_key = "my_secret_key_that_allows_access_to_my_s3_buckets"
  ssl = true
}

resource "minio_user" "some_s3_user_account" {
  access_key = var.s3_user.access_key_id
  secret_key = var.s3_user.secret_access_key
}

If I remove the minio_user resource, terraform init goes without issue but as soon as it's added back I get this:

bash-5.0# terraform init
Initializing modules...

Initializing the backend...

Initializing provider plugins...
...
- Using previously-installed refaktory/minio v0.1.0
...
- Finding latest version of hashicorp/minio...

Error: Failed to install provider

Error while installing hashicorp/minio: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/minio

I removed the .terraform directory to start fresh but I end up with the same result, it just downloads your provider without an issue:

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding refaktory/minio versions matching "0.1.0"...
...
- Finding latest version of hashicorp/minio...
...
- Installing refaktory/minio v0.1.0...
- Installing refaktory/minio v0.1.0...
- Installed refaktory/minio v0.1.0 (self-signed, key ID 6D55AB8B63A0B0C3)
...

I tried to give an alias to the minio provider definition and reference it in the minio_user resource without success I don't know why terraform looks for a hashicorp/minio provider whereas I have only yours installed.

it would be useful to be able to import existing resources:

resource "minio_bucket" "test" {
  name = "test"
}

terraform import minio_bucket.test test

The format chosen is somewhat similar to the one in the AWS terraform provider.

Example:

resource "minio_bucket" "xxxx" {
  name = "xxxx"

  lifecycle_rule {
    expiration {
      days = 2
    }
  }
}

The resource minio_canned_policy order of Action array shifts on second and further terraform plan forcing replacement of the resource.

Steps to reproduce:

1. Create main.tf

resource "minio_canned_policy" "backups" {
  name = "backups"

  policy = <<EOT
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::backups"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:PutObject",
                "s3:DeleteObject"
            ],
            "Resource": [
                "arn:aws:s3:::backups/*"
            ]
        }
    ]
}
EOT
}

2. Run terraform plan

  # minio_canned_policy.backups will be created
  + resource "minio_canned_policy" "backups" {
      + id     = (known after apply)
      + name   = "backups"
      + policy = jsonencode(
            {
              + Statement = [
                  + {
                      + Action   = [
                          + "s3:ListBucket",
                        ]
                      + Effect   = "Allow"
                      + Resource = [
                          + "arn:aws:s3:::backups",
                        ]
                    },
                  + {
                      + Action   = [
                          + "s3:GetObject",
                          + "s3:PutObject",
                          + "s3:DeleteObject",
                        ]
                      + Effect   = "Allow"
                      + Resource = [
                          + "arn:aws:s3:::backups/*",
                        ]
                    },
                ]
              + Version   = "2012-10-17"
            }
        )
    }

3. Run terraform apply

minio_canned_policy.backups: Creation complete after 1s [id=backups]

4. Run terraform plan again (without changing the resource)

  # minio_canned_policy.backups must be replaced
-/+ resource "minio_canned_policy" "backups" {
      ~ id     = "backups" -> (known after apply)
        name   = "backups"
      ~ policy = jsonencode(
          ~ {
              ~ Statement = [
                    {
                        Action   = [
                            "s3:ListBucket",
                        ]
                        Effect   = "Allow"
                        Resource = [
                            "arn:aws:s3:::backups",
                        ]
                    },
                  ~ {
                      ~ Action   = [
                          - "s3:DeleteObject",
                            "s3:GetObject",
                            "s3:PutObject",
                          + "s3:DeleteObject",
                        ]
                        # (2 unchanged elements hidden)
                    },
                ]
                # (1 unchanged element hidden)
            } # forces replacement
        )
    }

I suppose that this also applies to the Resource array but is not applicable here because it has only one element.

Thanks for putting your time into such a well documented provider.

Still, is this project maintained? It seems like e.g. the current minio release would not work, when looking at the docker-compose.yml you test with. It's only 1 disk and now etcd, this should block quiet some APIs?

Using your version, I cannot get the provider up and running, getting connection refused all the time. Using the console port, using localhost:9000 my self here too(non SSL), also using the user created by

    MINIO_ROOT_USER:
    MINIO_ROOT_PASSWORD:

Tried it with your minio/minio:RELEASE.2021-08-20T18-32-01Z and the current minio/minio:RELEASE.2021-11-24T23-19-33Z

Thanks!