feat: improve the builder actions and form validations

[rajesh-jonnalagadda]

Closes #2538

📑 Description

improve the builder actions and form validations

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
keep	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 11, 2024 1:40pm

[vercel]

@rajesh-jonnalagadda is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[rajesh-jonnalagadda]

@shahargl We are using Zod for form validation, which is currently configured to handle standard fields, standard tools(interval, incident, alert, assert, for each, threshold), and HTTP actions.

we can add zod-schema for other providers/tools too. if given the rules.

[Matvey-Kuk]

Hey @rajesh-jonnalagadda could you please fix tests? Thank you :)

[rajesh-jonnalagadda]

Hey @rajesh-jonnalagadda could you please fix tests? Thank you :)

I don't see any test failures; the only issue is that the Vercel deployment hasn't passed, as it requires approval from the internal team.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14884154	Triggered	Username Password	87afe69	elk/docker-compose-elk.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[talboren]

@rajesh-jonnalagadda there's a conflict in here, mind checking on it so we can wrap this up?