-
Notifications
You must be signed in to change notification settings - Fork 289
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
Fixes #37853 - Add OSTree remote option depth #11157
Fixes #37853 - Add OSTree remote option depth #11157
Conversation
876a2e1
to
e716980
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
Noticed one quick thing:
...sets/javascripts/bastion_katello/products/details/repositories/new/views/new-repository.html
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Later in the file there's the line:
test_url_root_options generic_remote_options: {include_refs: ['rawhide']}.to_json
What if you changed it to:
test_url_root_options generic_remote_options: {include_refs: ['rawhide'], depth: 1}.to_json
or something like that? That way, the test in test/services/katello/pulp3/repository_integration_test.rb
I think would pick it up and test the new parameter.
I'm going off of some assumptions since I haven't looked at generic content types for a while, but it's worth checking for more test coverage.
2cd9560
to
4d63cfe
Compare
Okay thanks for the review, lets see if there is really a VCR change necessary now, after the test addition 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just tested the PR, it's looking fine. I verified the depth is getting set on the Pulp remote:
...
}
],
"depth": 1,
"include_refs": [],
"exclude_refs": []
...
I also see the option to set the depth in hammer:
--deb-releases VALUE Whitespace-separated list of releases to be synced from deb-archive
--depth NUMBER An option to specify how many commits to traverse.
--description VALUE
4d63cfe
to
7fd897d
Compare
Looks like you just need to:
and upload the new VCRs. |
7fd897d
to
2d82f75
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, thank you!
What are the changes introduced in this pull request?
This PR adds the generic_remote_option
depth
to the OSTree repository type.Considerations taken when implementing this change?
I checked if the missing number types for the generic remotes is already available somewhere, and tried to keep the form the same.
The number type in the new-repository form has set a minimum value of 0, I am still not sure if this is the best place for that, but I also didn't want to add new variables as this might have been a serious undertaking for me, to get a new variable into the generic_remote_option function.
What are the testing steps for this pull request?
I have a testsystem setup on Foreman 3.11, where I edited the source, including version upgrade tests.