Unexpected SHA-256 hash for `21.9.2` release about terraform-provider-netapp-cloudmanager HOT 5 CLOSED

Hi @radeksimko , I deleted the old v21.9.2 and release a new version of v21.9.2. The terraform registry seems picked up the change(the doc is updated), but the release time is never updated as you indicate. By any chance, do you have a idea on how to fix this?

from terraform-provider-netapp-cloudmanager.

Generally speaking releases should be treated as immutable, i.e. you shouldn't really be deleting releases. I'm not sure if the Registry has a way of marking old releases in some way, but I imagine that such mechanism would only be relevant if that release has a significant vulnerability or is broken for most users, i.e. presents a high enough risk that warrants such action.

Do you mind sharing the reason for deletion of the old version?

Either way I would recommend cutting a new patch version (21.9.3).

from terraform-provider-netapp-cloudmanager.

I am okay with publishing a new patch version. But is there a way to fix 21.9.2 so that it's not in broken state? Should I replace it with the old version?

from terraform-provider-netapp-cloudmanager.

If you have the original old release assets and can re-upload the assets to GitHub under the same version then yes - I think that might fix it - alternatively/additionally I'd advise you contacting the TF Registry team on [email protected] as they are better equipped to answer such questions

from terraform-provider-netapp-cloudmanager.

Replace with the old version of 21.9.2 and it works fine.

from terraform-provider-netapp-cloudmanager.