Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RHOAIENG-15242: ref(manifests): add some newlines and indentation into the json strings with package version information #760

Merged

Conversation

jiridanek
Copy link
Member

@jiridanek jiridanek commented Nov 2, 2024

https://issues.redhat.com/browse/RHOAIENG-15242

Description

Previously, we used to have every json string on a single line, which meant we had long hard-to-read lines in our manifests. Now there is some human-friendly indentation in the files so it should be easier to read.

This is to have no impact on the data stored, it is a code formatting change only.

image

How Has This Been Tested?

I've ran the sample code from a comment on https://issues.redhat.com/browse/RHOAIENG-15333 that extracts and formats the installed software fields as a Markdown table. I then compared the outputs before and after this change, and looked for differences.

poetry run ci/package_versions.py > after.md
poetry run ci/package_versions.py > before.md
diff before.md after.md

Then I took the manifests and deployed them on some cluster

oc login --web
cd manifests/base
../../kustomize-5.0.2 edit set namespace redhat-ods-application
../../kustomize-5.0.2 edit set nameprefix main-
../../kustomize-5.0.2 build . | oc apply -f -

and then I also remembered to do it with overlays/additional images.

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

…o the json strings with package version information

Previously, we used to have every json string on a single line, which meant we had long hard-to-read lines in our manifests.
Now there is some human-friendly indentation in the files so it should be easier to read.

This is to nave no impact on the data stored, it is a code formatting change only.
@jstourac
Copy link
Member

jstourac commented Nov 2, 2024

/lgtm

@atheo89
Copy link
Member

atheo89 commented Nov 4, 2024

/lgtm

However, I was checking the test instructions and you mentioned this:

poetry run ci/package_versions.py > after.md
poetry run ci/package_versions.py > before.md
diff before.md after.md

What are you talking about? Did i miss something? I search for package_versions.py on your fork and it is not there a sucj file 🤔

@caponetto
Copy link
Contributor

/lgtm TY!

@jiridanek
Copy link
Member Author

What are you talking about? Did i miss something? I search for package_versions.py on your fork and it is not there a such file 🤔

It's in a comment in a Jira,

I've ran the sample code from a comment on https://issues.redhat.com/browse/RHOAIENG-15333 that extracts and formats the installed software fields as a Markdown table.

@jiridanek
Copy link
Member Author

/approve

Copy link
Contributor

openshift-ci bot commented Nov 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiridanek

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@jiridanek
Copy link
Member Author

jiridanek commented Nov 4, 2024

/override ci/prow/images
rocm images failed to build, same old

@openshift-ci openshift-ci bot added the approved label Nov 4, 2024
Copy link
Contributor

openshift-ci bot commented Nov 4, 2024

@jiridanek: Overrode contexts on behalf of jiridanek: ci/prow/images

In response to this:

/override ci/prow/images

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-merge-bot openshift-merge-bot bot merged commit fd6e6af into opendatahub-io:main Nov 4, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants