We wanted to expand our infrastructure provider support and our users love Terragrunt ! Users can now leverage Terragrunt to provision infrastructure and application resource dependencies through Harness.
terragrunt plan
terragrunt apply
terragrunt output
terragrunt destroy
Check out the Docs
This Feature is behind feature flag (TERRAGRUNT). Please reach out to Harness support to enable for your account. Happy Deploying 🚀
Harness users now have the ability to templatize the Cloud Provider in the CloudFormation Delete Stack.
Checkout the docs
Users can now deploy their applications and services into their Azure GovCloud Environment. Users can define their CD Processes and pick Azure GovCloud Region and Azure GovCloud resources for environments and integrations for deployment.
This Feature is behind feature flag. Please reach out to Harness support to enable for your account. Happy Deploying 🚀
Users can now query information about the infrastructure definition through the Harness API.
GovCloud is used by organizations such as government agencies at the federal, state, and local level, as well as contractors, educational institutions. It is also used for regulatory compliance with these organizations.
Harness now allows users to deploy to their AWS GovCloud Environments. Checkout the docs
This Feature is behind feature flag(AWS_OVERRIDE_REGION ). Please reach out to Harness support to enable for your account. Happy Deploying 🚀
Harness can use one or more AWS Elastic Load Balancers (ALB and NLB only) for your Amazon ECS service to distribute traffic evenly across the tasks in your service.
Check out our Docs!
This Feature is behind feature flag(ECS_MULTI_LBS) . Please reach out to Harness support to enable for your account. Happy Deploying 🚀
Now, the users can enforce that an API key needs to be provided in the headers for all the webhook triggers of the application. Only if the API key has the access to deploy, the trigger will get invoked else not. This secures our triggers better.
Check out the Docs!
This Feature is behind the feature flag WEBHOOK_TRIGGER_AUTHORIZATION. Please reach out to Harness support to enable for your account. Happy Deploying 🚀
What is a Capacity Provider?
A capacity provider is associated with a cluster and is used in a capacity provider strategy to determine the infrastructure that a task runs on.
Harness Enhancement
You can use a Capacity provider strategy in your ECS Service definition via the capacityProviderStrategy parameter.
Check out the Docs
By default, the Harness Kubernetes Delegate uses a ClusterRoleBinding to the default service account. Instead, you can use AWS IAM roles for service accounts (IRSA) to associate a specific IAM role with the service account used by the Harness Kubernetes Delegate.
Check out the Docs
This Feature is behind feature flag [IRSA _ FOR _ EKS]. Please reach out to Harness support to enable for your account. Happy Deploying 🚀
User's can now fetch their manifests from non GitHub sources. This means that users can fetch their manifests from S3, Aritfactory, and Nexus and unpackaged those for Harness deployment. Currently this feature supported for Kubernetes and Openshift manifests. We are working to support this functionality for Helm and Cloud Foundry. Check out the Docs
This Feature is behind feature flag [CUSTOM_MANIFEST]. Please reach out to Harness support to enable for your account. Happy Deploying 🚀