feat: deprecate and archive prebuilt bindings for hashicups provider #251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: team-tf-cdk <[email protected]>
[
|
[
|
[
|
[
|
[
|
[
|
[
|
[
|
xiehan
requested review from
mutahhir and
Maed223
and removed request for
a team
[
|
[
|
[
|
[
|
|
I'm going to lock this pull request because it has been closed for at least 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue so we can investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HashiCorp has made the decision to stop publishing new versions of prebuilt Terraform
hashicupsprovider bindings forCDK for Terraform. Once this PR is merged, the cdktf/cdktf-provider-hashicups repository will be archived and will no longer
be supported in any way by HashiCorp. Previously-published versions of the prebuilt
hashicupsprovider will still continueto be available on their respective package managers (e.g. npm, PyPi, Maven, NuGet), but these will not be compatible with
new releases of
cdktfand are no longer eligible for commercial support.Please complete the following steps in this exact order to complete the deprecation process:
provider.json,sharded-stacks.json, andprovidersWithCustomRunners.jsonin this PR for any syntax errors caused by extraneous commasrelease_mavenjob completed successfullyHashiCorp.Cdktf.Providers.Hashicupspackage in NuGet Gallery (optional but recommended)Please also ensure that not too much time passes in between each of these steps. Notably, if the PR in the provider repo is
merged but other changes are deployed before that repo is properly archived, there could be unintended behavior. So, it is
highly recommended that you complete the above steps in short succession.