OAPE-307: Add script to automatically update tekton config version

[chiragkyal]

The script is generated by Cursor using claude-4-sonnet

Prompts used

Prompt 1

Create a script that updates Tekton pipeline YAML files with new version numbers. The script should:

1. Rename files from old version patterns (e.g. 1-17) to new version patterns (e.g. 1-18)
2. Update all version references within the files
3. Handle different components with different version inputs:
   - cert-manager-operator: version like v1.18.0
   - cert-manager-istio-csr: version like v0.14.2  
   - jetstack-cert-manager: version like v1.18.2
4. Include command-line options for each component version
5. Make the script configurable with proper documentation

The script should update:
- Filenames: 1-17 → 1-18
- Content references: 1.17 → 1.18
- Release versions: RELEASE_VERSION=v1.17.0 → RELEASE_VERSION=v1.18.0

Prompt 2

This is an edge case. Modify the script to handle a special scenario for cert-manager-istio-csr files:
- File names and version references should follow the pattern (1-17 → 1-18)
- BUT the RELEASE_VERSION should use the istio-csr specific version (i.e v0.14.2)
- All other components should use their provided version for both file naming and RELEASE_VERSION

Add logic to automatically determine the file version pattern from other component versions when only istio-csr version is provided.

Prompt 3

The script is making unwanted changes when run multiple times on already-updated files. Make sure the script should be safe to run multiple times without making unwanted modifications.

Additionally 
- Ensure the script fails gracefully if required parameters are missing
- Handle cases where no files match the expected patterns
- A detailed README with usage examples

/cc @bharath-b-rh

[openshift-ci-robot]

@chiragkyal: This pull request references OAPE-307 which is a valid jira issue.

Details

In response to this:

The script is generated by Cursor using claude-4-sonnet

Prompts used

Prompt 1

Create a script that updates Tekton pipeline YAML files with new version numbers. The script should:

1. Rename files from old version patterns (e.g. 1-17) to new version patterns (e.g. 1-18)
2. Update all version references within the files
3. Handle different components with different version inputs:
  - cert-manager-operator: version like v1.18.0
  - cert-manager-istio-csr: version like v0.14.2  
  - jetstack-cert-manager: version like v1.18.2
4. Include command-line options for each component version
5. Make the script configurable with proper documentation

The script should update:
- Filenames: 1-17 → 1-18
- Content references: 1.17 → 1.18
- Release versions: RELEASE_VERSION=v1.17.0 → RELEASE_VERSION=v1.18.0

Prompt 2

This is an edge case. Modify the script to handle a special scenario for cert-manager-istio-csr files:
- File names and version references should follow the pattern (1-17 → 1-18)
- BUT the RELEASE_VERSION should use the istio-csr specific version (i.e v0.14.2)
- All other components should use their provided version for both file naming and RELEASE_VERSION

Add logic to automatically determine the file version pattern from other component versions when only istio-csr version is provided.

Prompt 3

The script is making unwanted changes when run multiple times on already-updated files. Make sure the script should be safe to run multiple times without making unwanted modifications.

Additionally 
- Ensure the script fails gracefully if required parameters are missing
- Handle cases where no files match the expected patterns
- A detailed README with usage examples

/cc @bharath-b-rh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chiragkyal]

@coderabbitai review

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[bharath-b-rh]

/lifecycle frozen

[openshift-ci]

@bharath-b-rh: The lifecycle/frozen label cannot be applied to Pull Requests.

Details

In response to this:

/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[bharath-b-rh]

/remove-lifecycle rotten

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[bharath-b-rh]

/lgtm
/approve

/cherrypick release-1.17
/cherrypick release-1.19

[openshift-cherrypick-robot]

@bharath-b-rh: once the present PR merges, I will cherry-pick it on top of release-1.17, release-1.19 in new PRs and assign them to you.

Details

In response to this:

/lgtm
/approve

/cherrypick release-1.17
/cherrypick release-1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh, chiragkyal

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [bharath-b-rh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-cherrypick-robot]

@bharath-b-rh: new pull request created: #821

Details

In response to this:

/lgtm
/approve

/cherrypick release-1.17
/cherrypick release-1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@bharath-b-rh: #497 failed to apply on top of branch "release-1.19":

Applying: Add script to automatically update tekton config version
Applying: Add Makefile target
.git/rebase-apply/patch:44: trailing whitespace.
# 
.git/rebase-apply/patch:51: trailing whitespace.
#   
.git/rebase-apply/patch:54: trailing whitespace.
#   
.git/rebase-apply/patch:57: trailing whitespace.
#   
.git/rebase-apply/patch:28: new blank line at EOF.
+
warning: 5 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	Makefile
Falling back to patching base and 3-way merge...
Auto-merging Makefile
CONFLICT (content): Merge conflict in Makefile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 Add Makefile target

Details

In response to this:

/lgtm
/approve

/cherrypick release-1.17
/cherrypick release-1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.