: [DISCUSS] New terraform git tag for registry workaround
All,
I got the following from TF support:
Hello there, provider versions are immutable in the registry. Therefore, when
you deleted and recreated the version in Github, the hash has changed, and the
registry will refuse to serve it. Your
Subject: Re: [DISCUSS] New terraform git tag for registry workaround
I think your proposals are ok as an ad-hoc solution to the current
situation @Rohit Yadav . I wonder how we should deal with this in the
future though.
1. As for the numbering, do we have a procedure to prevent this issue
in the
] New terraform git tag for registry workaround
I think your proposals are ok as an ad-hoc solution to the current
situation @Rohit Yadav . I wonder how we should deal with this in the
future though.
1. As for the numbering, do we have a procedure to prevent this issue
in the future?
2. The provider
I think your proposals are ok as an ad-hoc solution to the current
situation @Rohit Yadav . I wonder how we should deal with this in the
future though.
1. As for the numbering, do we have a procedure to prevent this issue
in the future?
2. The provider is part of apache and I think the link
https:
All,
The recent Terraform provider release v0.5.0 has a problem with the Terraform
registry website.
https://github.com/apache/cloudstack-terraform-provider/issues/109
The registry support isn't able to provide a resolution now, their manual
resync button on the provider isn't fixing the issue
