Customers will now have the ability to support custom headers and/or bearer tokens while setting up the Prometheus connector. This improvement will drive adoption of CV among customers who use Prometheus with bearer token based authentication mechanisms.
Customers will now be able to reuse identifiers of deleted entities. Earlier, in Harness Platform, we took the approach to soft-delete entities and that prevented users from reusing identifiers after deletion. Now, with this change, we hard-delete entities and that will allow customers to reuse identifiers after deletion.
However, caution must be exercised while reusing identifiers as any history of the deleted entity in audit logs will start to now map to new entity using the same identifier.
We will make this functionality enabled for all customers but for now this is behind FF: HARDDELETEENTITIES
AWS ECS Task Definition now supports Runtime Platform option. Runtime Platform Option enables to specify the Operating System and CPU Architecture as part of the Task Definition. AWS Java SDK is upgraded from version 1.12.47 to 1.12.220 with this improvement.
Added support to add the continuous verification output to a variable that will be available in the PIPELINE or WORKFLOW scope. This allows the user to ignore the continuous verification failures without rollback and check the status at a later stage.
[New] We have added support for basic authentication for prometheus endpoints in the connector setup for the continuous verification workflows. This allows the customer to authenticate their credentials with their hosted prometheus using Harness Secrets.
Now you can override your values.yml at the K8s Apply step in a workflow. You can do it either inline or remote (via Git repositories).
This makes the deployment more flexible as now you can have multiple Apply steps in a workflow and then override the values at runtime as well.
We are supporting the instance sync for SSH deployments (PDC, AWS & Azure) by which the service dashboard will contain the real-time values of instances that are up for these services.
Users now have the ability to resolve tags during execution and won’t need to wait until the end.
Now we are supporting exponential backoff strategy for all the CF operations. With this if there is any failure in a cloud formation step, it won't fail by retry.
This is going to be configurable by setting some account-level defaults.
You can refer to the docs to know more about it here
Earlier for SSH and WinRm deployments, in Select Nodes step user can choose to deploy specific hosts and choose from a list of hosts added previously in Infrastructure Definition.
Now you can specify hosts which are not present in Infrastructure Definition. Doc reference is here
User can also choose hosts which are not defined in Infrastructure Definition for SSH deployments on Start New Deployment screen with the option to target specific hosts enabled.
Doc reference is here
This is behind a feature flag: DEPLOY_TO_INLINE_HOSTS
