We constantly improve different aspects of HELM3 deployments in collaboration with our partners. This section lists updates and improvements done in this round.
You can now configure the number of failed login attempts allowed before users are locked out of the system.
We added a new variable
MAX_LOGIN_ATTEMPTS to the HELM3 secrets chart. You may set this variable according to your own requirements. The default value is set to five (5). Here is how we calculate this number:
MAX_LOGIN_ATTEMPTSthen your user will be locked out of the system. To unlock such users the tenant administration must first disable 2FA for this user and instruct users to navigate
/forgotaddress of the tenant to reset their password. This will reset the counter and user can login again.
Information in this section is intended for our customers who use OEM version of the elastic.io platform.
The platform builds a component docker image every time you push a new version of your component. When you remove the component or a particular version of it from the platform, an associated docker build will remain until you would remove it at later stage directly from the docker registry.
With this update we improved the situation in the following way:
remove-deleted-repos-from-docker) to help cleanup the remnant builds. Contact us to get a copy of this tool.
Update Objectactions removed in favor the new
Make a Paymentaction
Add new Subscriberaction
As a part of our on-going improvements of integration components, we
Here is the list of components for 22.18.1 release.
2.0.12. Both deprecated and V2 were updated.