[SECURESIGN-79] DAST testing

[bouskaJ]

Summary by Sourcery

Add a new Tekton-based DAST workflow that provisions a fresh cluster, installs the operator and TAS components, and runs dynamic security scans using RapiDAST on the deployed Fulcio service

New Features:

• Introduce a Tekton pipeline (operator-dast) to perform dynamic application security testing (DAST) on TAS deployments

Enhancements:

• Provision an ephemeral EaaS space and Hypershift AWS cluster for testing
• Conditionally install the operator from bundle, image, or FBC based on parsed metadata
• Integrate Keycloak and TAS installations into the pipeline before scanning

Tests:

• Add a RapiDAST step to execute API and active scans against the Fulcio service

Chores:

• Add IntelliJ .idea project configuration files

[sourcery-ai]

Reviewer's Guide

This PR adds a new Tekton-based DAST testing pipeline for TAS deployments, implements supporting StepAction resources for cloning operator repositories and installing TAS, and includes IDE project configuration files.

File-Level Changes

Change	Details	Files
Introduce a comprehensive DAST testing pipeline in Tekton	Define pipeline parameters and description for TAS DAST testing Add tasks: parse-metadata, provision-eaas-space, provision-cluster with inline taskSpec Include conditional install-operator steps (bundle, image, FBC) based on component Implement a dast-test taskSpec with credential setup, keycloak/TAS installation, URL resolution, and RapiDAST scan	pipelines/rhtas-operator-dast.yaml
Add StepAction to clone operator repository	Define params for repository, component, git URL/revision Mount repository volume and set env vars Implement script logic to clone appropriate operator source	stepactions/git-clone-operator.yaml
Add StepAction to install TAS from repository	Define params for credentials, repository, workdir, KUBECONFIG Mount credentials and repository volumes Script patches sample CR, creates namespace, applies manifest, and waits for readiness	stepactions/install-tas.yaml
Include IDE project configuration files	Add .idea modules.xml, pipelines.iml, vcs.xml, and workspace.xml	.idea/modules.xml .idea/pipelines.iml .idea/vcs.xml .idea/workspace.xml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.