Comments (16)
v1.20.0 published! π
![image](https://private-user-images.githubusercontent.com/418083/280496536-50b05aeb-b869-4c1a-89f9-bd4f0cca111b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQyMTk0NjksIm5iZiI6MTcwNDIxOTE2OSwicGF0aCI6Ii80MTgwODMvMjgwNDk2NTM2LTUwYjA1YWViLWI4NjktNGMxYS04OWY5LWJkNGYwY2NhMTExYi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEwMlQxODEyNDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00OGU1YTJlNTE1YTM3YzEwYWQ4Mjg3ZmJhYTUxMmI3YzBmNjE1ZjA0ZGQzYTY1ZTdlOTc3MGQwZTU3ZjM3NTEyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.OqVJhfTWtFKZYDoeJZsNT4IU3Y1jIcrJ5bmEsNm_guA)
![image](https://private-user-images.githubusercontent.com/418083/280496526-18a90bae-e5a9-4942-a4f6-c2a48691edad.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQyMTk0NjksIm5iZiI6MTcwNDIxOTE2OSwicGF0aCI6Ii80MTgwODMvMjgwNDk2NTI2LTE4YTkwYmFlLWU1YTktNDk0Mi1hNGY2LWMyYTQ4NjkxZWRhZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEwMlQxODEyNDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zMDg0Y2JkNmJmMmM0MTE0ODgxYTkzNWI1YzFlM2M4ZGJlYmU0MTk2MDg3OTZhYjJiZmIyMmVkMTMzYzNiODM2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.18m4YfvbXieRu9IMzhbPNrtORfNWGVkdsZ6JOUVfUCs)
![image](https://private-user-images.githubusercontent.com/418083/280496490-eb86af64-a051-46c6-b296-677fc415b3aa.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQyMTk0NjksIm5iZiI6MTcwNDIxOTE2OSwicGF0aCI6Ii80MTgwODMvMjgwNDk2NDkwLWViODZhZjY0LWEwNTEtNDZjNi1iMjk2LTY3N2ZjNDE1YjNhYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEwMlQxODEyNDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kMzg1NWFiZmQ0MmQxNzdjOTU3NzEzNWM4YjMxMzM4YWM3Y2I5MjJhYzcwMTdiNmRjMjBkODk3ODc1NDk1NzQyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.5sh0a70eZjrEBM1qXxa1WGtDTxI1Oe0XqR1vXC8TPm4)
![image](https://private-user-images.githubusercontent.com/418083/280496698-4d77c030-bce6-4f4c-a627-9cdeefa8e468.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQyMTk0NjksIm5iZiI6MTcwNDIxOTE2OSwicGF0aCI6Ii80MTgwODMvMjgwNDk2Njk4LTRkNzdjMDMwLWJjZTYtNGY0Yy1hNjI3LTljZGVlZmE4ZTQ2OC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEwMlQxODEyNDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lNGI4Y2FkMTg0NDcyNTdiMTU5ZTVkYmJiYWE2NjE4YTI0MWJhNzJhYWI1NTc4YzA1MjdkNTFjYTM4MWVjOTJmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.CdxGrOalqHdvfJ9lAhyPDETiZptypgiLQT1oVy82rAQ)
from terraform-provider-minio.
Thanks for publishing a new release π
I can confirm that 1.20 is working fine.
Switching to a new repo/namespace in the future would be nice
from terraform-provider-minio.
Thank you @felladrin
I'll stick to 1.18.0 for now as a temporary workaround
from terraform-provider-minio.
We're finding the same issue but sticking with v1.18.0 has worked as a workaround.
from terraform-provider-minio.
If I may add my two cents, wouldn't it be easier to create a new gpg key and publish under the new repo name as well as the old repo for the first few patches/minors and eventually transition into just using the org one?
I'm no where near an expert and don't know if there are licensing fees and such but it seems like an idea.
Tl;dr;
Support both. publish for a bit (new + old) providers.
Deprecate the old provider and encourage people to transition to the new provider
Ending support/features/security updates at a set time for the old provider.
from terraform-provider-minio.
Indeed! Forking/mirroring might happen later, considering we still have that other intricate issue to solve.
In all cases, the original repo has to be back in place for the current provider to get back working.
But one issue at a timeπ€
from terraform-provider-minio.
Yeah, working for us as well. Thanks @felladrin
from terraform-provider-minio.
You're right about the assets. I didn't catch them on the release page, sorry about that π
Still, install fails so there must be another reason
from terraform-provider-minio.
Same with me, using terraform 1.6.2
from terraform-provider-minio.
Published v1.19.0, including #520, but the shasums_url continue pointing to the previous repo.
We'll contact HashiCorp support to check what can be done. (Databricks has been through the same process)
from terraform-provider-minio.
Just to let you know that we're currently waiting for HashiCorp's support response on this.
from terraform-provider-minio.
Alright, everyone, we got a detailed response from one of the engineers from the Terraform Registry team, and, in summary, there's no way to change the provider in the Registry (aminueza/minio) for it to use the repository under our new organization.
Click here for more details.
Since the provider in the Registry is highly attached to the GitHub auth system (the namespace of the provider must match the GitHub owner), to publish new versions of the provider from this repository (https://github.com/terraform-provider-minio/terraform-provider-minio), it'd need to be done through an entirely new provider.Considering the situation, and also all the users that rely on this provider, here's what's going to happen next:
We'll move the repository back under aminueza's GitHub account, update the GPG key and literal URLs in the code, and finally publish v1.20.0 in the registry, which won't suffer from the Failed to install provider
issue anymore.
Extra info: We won't dissolve the github.com/terraform-provider-minio organization because it will be redirecting the traffic to aminueza's repo and also because it might be useful for forks/sibling repos later. The advantage of having an organization is that the maintainers have more autonomy over the repositories.
from terraform-provider-minio.
Thanks for letting us know!
Will double-check the release workflow.
from terraform-provider-minio.
π€ I see the shasum file is available at https://github.com/terraform-provider-minio/terraform-provider-minio/releases/tag/v1.18.3, and the shasum for terraform-provider-minio_1.18.3_linux_amd64.zip
is there:
![image](https://private-user-images.githubusercontent.com/418083/277625325-7771dcc1-6b44-4443-9886-2c8ddc8a7e8d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQyMTk0NjksIm5iZiI6MTcwNDIxOTE2OSwicGF0aCI6Ii80MTgwODMvMjc3NjI1MzI1LTc3NzFkY2MxLTZiNDQtNDQ0My05ODg2LTJjOGRkYzhhN2U4ZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEwMlQxODEyNDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02MWFlZDhmYjg5YjI1MjFjNDA2YTgxNTc0MzFkNmI4MDY1ZGVlMGZlOGYyZTc1ZTUzZjlhNTcwYzkwOWMwNzhjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.pj0Sumou85umtMTyBIgMXGiPjOwM5PTF9NwdaZxm9Ug)
The published files in these release match the number of the files released in the previous one (v1.18.0).
from terraform-provider-minio.
Indeed.
I can't investigate deeper now, but I will do it soon.
Please keep me posted if you find out anything new about this issue.
[I doubt it, but this could be related to the repository address, which was changed recently.]
from terraform-provider-minio.
π‘ I think the issue is really about the repository address. I checked the response of these two URLs:
- https://registry.terraform.io/v1/providers/aminueza/minio/1.18.0/download/linux/amd64 (when it was on the previous repo)
- https://registry.terraform.io/v1/providers/aminueza/minio/1.18.3/download/linux/amd64 (released from the current repository)
And the shasums URL hasn't been updated.
Previous | Current |
---|---|
![]() |
![]() |
The sad thing is that there's no option in Terraform Registry provider settings to change the repository ULR of a released provider.
from terraform-provider-minio.
Related Issues (20)
- Recreate deleted (missing) resources instead of [FATAL]ing
- Add support for server-side replication HOT 1
- `minio_iam_service_account` resource keeps dropping policy. HOT 2
- Add NonCurrentVersionExpiration to Lifecycle Management Rules
- Module publishing - Terraform Registry HOT 7
- Add a description for every attribute in the documentation
- Missing checksum list for 1.19.0 HOT 2
- terraform providfer does not work if api minio is running via proxy on port 443 HOT 1
- [Feature Request] Consider replacing Adminio-UI with the native MinIO Console
- [Feature_request] Set Expire delete marker on noncurrent_version_expiration_days life cycle management rule
- Lifecycle rule with noncurrent_version_expiration_days causes a update every plan/apply in 2.0.0 HOT 4
- minio_iam_service_account resource is updated on every run in 2.0.0 HOT 13
- Returned bucket_domain_name is wrong HOT 1
- [BUG] Root object was present, but now absent.
- [FATAL] unable to read policy: The canned policy does not exist
- Allow STS credentials instead of username/password HOT 1
- [FATAL] putting object failed (): one of source / content / content_base64 is not set
- [ilm] tier transitioning
- How create a folder into a specified bucket
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-minio.