Customizable Folder/File Path for ProwJob inrepo Definitions

[zppinho]

What would you like to be added:
Currently Prow allows for the definition of Jobs in the same repository as the code Inrepoconfig and this can be done with a .prow directory or .prow.yaml file.
See inrepoconfig
We would like to have the possibility to choose the folder or file path where these Jobs can be defined
e.g: .cicd/.prow/triggers.yaml
This defnition could be set in the config.yaml of prow:

in_repo_config:
  enabled:
    org/repo: true
    triggers_path: ".cicd/.prow/"

Why is this needed:
This enables the centralization of all CI/CD definitions in a dedicated folder within the repository. Which enhances the overall readability of the repository, minimizing confusion for new developers.

[zppinho]

/sig testing

[cfradewavecom]

+1

[liangyuanpeng]

/area prow

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[BenTheElder]

If you're still interested in this feature please file with the project's newly split out repo at https://github.com/kubernetes-sigs/prow

Unfortunately don't think we have maintainers with the bandwidth for feature requests like this currently and Kubernetes intentionally does NOT use inrepoconfig ourselves for security reasons.