Helm Resource Provider - Retirement Notice
troy-ameigh opened this issue · comments
We would like to inform you that the functionality provided by the following CloudFormation Public Resources has been superseded with functionality in Amazon EKS Blueprints.
On 03/31/2023. Support for this Public Resource type will be retired. This means that no support for this resource type. You will still be able to clone the GitHub repositories and use the code (which is in the "Maintenance" branch), however you will be required to deploy them as a Private Registry type (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry-private.html). If you decide to deploy them as a Private Registry type, you will be required to maintain the code on your own.
Existing deployments will continue to run. If underlying service APIs change after moving to this maintenance mode, deployments may error or may not be possible to stop / start.
It is recommended that you migrate to EKS Blueprints. EKS Blueprints helps you compose complete EKS clusters that are fully bootstrapped with the operational software that is needed to deploy and operate workloads. With EKS Blueprints, you describe the configuration for the desired state of your EKS environment, such as the control plane, worker nodes, and Kubernetes add-ons, as an IaC blueprint. Once a blueprint is configured, you can use it to stamp out consistent environments across multiple AWS accounts and Regions using continuous deployment automation. EKS Blueprints is provide in two deployment types: CDK and Terraform.
More information is available via SERVICE documentation ”Amazon EKS Blueprints - CDK (https://aws-quickstart.github.io/cdk-eks-blueprints/)” or “Amazon EKS Blueprints - Terraform (https://aws-ia.github.io/terraform-aws-eks-blueprints/)“]
You will still be able to clone the GitHub repositories and use the code
This appears to be untrue, at least for license-sensitive organizations, since none of the code contains any license files nor licensing text. This situation is now even more complicated since the head of the repo nuked all the code that someone would want to use
No one asked me, but this was indescribably rude and will for sure ensure that I never trust AWS quickstarts ever again for anything
@mdaniel I have addressed your concern around the license file, which is now in the repo. All QuickStarts are developed under the Apache 2.0 license. As for the code, the latest code is in the maintenance branch, so after you fork down the repo, switch to that branch and you will see all the code, that you need.
Hi,
Even if I try to register it as a private resource all I got is:
"ProgressStatus": "FAILED",
"Description": "Deployment is currently in VALIDATION_STAGE of status FAILED; Next is DEPLOY_STAGE with status CANCELLED\nDeployment failed with error. Error message: [38ed2569-7f18-4cd2-a620-441a35d1fdd3] One or more of the following files are missing from the input artifact: [schema.json, .rpdk-config, lambda deployment package]"
I am using the code from the "maintenance" branch.
Has anyone tried as well?
Thanks