replaced repo names with generic value - #1409
Conversation
|
Not a -1 but i'm wondering how likely these are to change between RHEL releases. It looks to me like the values are the same regardless if it's 9.2 or 9.6, for example. What would change is the value above in |
After discussing with RelDel and other stakeholders, we decided to replace specific repo names with generic values to reduce maintenance any time a RHEL lifecycle ends. I think it happens every couple of years, but we'd still have to remember to update the docs each time. |
|
NOTE: I added the do-not-merge/hold label until I receive feedback from additional stakeholders about the downstream MR. |
6b87849 to
65685da
Compare
|
@jistr I added numbers to the repository placeholder values, as suggested by a peer reviewer. |
|
/lgtm |
|
/lgtm |
@ciecierski or @jistr Can you approve the PR so it can merge? |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
c2642cf
into
openstack-k8s-operators:main
|
/cherry-pick 18.0-fr5 |
|
@klgill: new pull request created: #1419 DetailsIn response to this:
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. |
6 participants
https://redhat.atlassian.net/browse/OSPRH-25243
I replaced repo names with a generic value and added a link to a KCS that lists the required repositories for RHOSO.
This change affects multiple guides.