Closed team-tf-cdk closed 8 months ago
custom-constructs
] Terraform Plan πsuccess
Pusher: @team-tf-cdk, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos-partners
] Terraform Plan πsuccess
Pusher: @team-tf-cdk, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos-official-new
] Terraform Plan πsuccess
Pusher: @team-tf-cdk, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos
] Terraform Plan πsuccess
Pusher: @team-tf-cdk, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos
] Terraform Plan πsuccess
Pusher: @team-tf-cdk, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
custom-constructs
] Terraform Plan πsuccess
Pusher: @xiehan, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos-partners
] Terraform Plan πsuccess
Pusher: @xiehan, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos-official-new
] Terraform Plan πsuccess
Pusher: @xiehan, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
repos
] Terraform Plan πsuccess
Pusher: @xiehan, Action: pull_request_target
, Working Directory: `, Workflow:
Plan`
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.
HashiCorp has made the decision to stop publishing new versions of prebuilt Terraform
template
provider bindings for CDK for Terraform. Once this PR is merged, the cdktf/cdktf-provider-template repository will be archived and will no longer be supported in any way by HashiCorp. Previously-published versions of the prebuilttemplate
provider will still continue to be available on their respective package managers (e.g. npm, PyPi, Maven, NuGet), but these will not be compatible with new releases ofcdktf
and 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.json
in this PR for any syntax errors caused by extraneous commasrelease_maven
job completed successfullyHashiCorp.Cdktf.Providers.Template
package 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.