Enable Tekton step-actions

[enarha]

This is already enabled and used in Konflux (see https://github.com/redhat-appstudio/infra-deployments/pull/3693 and https://github.com/redhat-appstudio/infra-deployments/pull/3818). Without having the configuration in pipeline-service, updates were overriding the values. This will not generate diff in Konflux.

[enarha]

did not realize the delete was occuring on the merge

more motivation perhaps @enarha to move forward with something like redhat-appstudio/infra-deployments@main...gabemontero:infra-deployments:copy-over-plnsrvce-2 and run kustomize build ... on the two spots in this repo in components/pipelines and then add the grafana panels and be done with his, no?

Generally speaking, yeah, I agree we should move away from pipeline-service. Few drawbacks I can think of are:

• I like when the bot opens the PR, as I can lgtm it, which I can't do on PRs opened by me ;-).
• It's harder to find the pipeline-service related PRs, we usually have 1 with a standard subject which is easy to find.
• More conflicts to resolve. With one updated PR, there are no conflicts with the auto generated deploy.yamls.

but these are small issues.

[enarha]

/test test-pipeline-service-upgrade-ocp-414

[enarha]

/test test-pipeline-service-deployment-ocp-414

[enarha]

/test test-pipeline-service-upgrade-ocp-414

[enarha]

/test test-pipeline-service-deployment-ocp-414

[gabemontero]

FYI for those besides @enarha and myself, these technically intermittent but pretty persistent issues accessing the provisioned ROSA clusters is getting worked in https://redhat-internal.slack.com/archives/C032EJ007C0/p1720725499450859 .... currently trying to sort out with the infra team why @xinredhat cannot access the konflux-ci namespace

[gabemontero]

given this setting was working before @enarha feel free to merge without the CI passing ... I'll refrain from doing it myself in case there was something you wanted to confirm

[enarha]

tested manually, tests passed.