-
Notifications
You must be signed in to change notification settings - Fork 155
Added support for subresources. #968
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
base: main
Are you sure you want to change the base?
Conversation
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 18s |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 35s |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 25s |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 23s |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 15s |
@beeankha can you please run the workflows again? I'd make the changes where the previous one failed on:
Thanks! |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 23s |
e35bc45
to
9674509
Compare
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 27s |
@beeankha I see that the workflow this time failed on one of the few commits that were merged into main in the meantime, while I was working on this item. I checked out the latest version of the original main and cherry-picked the changes I made and pushed it back to my own main branch. Everything should be okay now. And, maybe it's done on purpose, but why is there no |
@beeankha sorry for disturbing you with this, but can you maybe tell me how I can get my 2 PRs reviewed and (planned) to be merged into master / the next version? And if there are better channels to communicate in about changes to community collections like this one, can you please share them with me too? Thanks! |
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.
Besides a version_added
, it's LGTM
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 29s |
Hi @yorick1989, the failed sanity (that was not related to your PR) got resolved. Could you please rebase your PR or merge master to your branch to have successful CI tests |
Why are there keep coming changes to the main branch while i'm waiting for almost 2 months now to have my pull requests in main? If the PR is not wanted to be pulled in main, just reject it. The same with the other, old, pull requests that are open for years now. I really don't understand why it is so hard to have such small PRs reviewed. If there is some process or communication line that can be used for discussing PRs, please let me know and put it in the documentation somewhere. Thanks |
Hi @yorick1989 , thank you for this PR (as well as #971), and apologies for the lack of responses to your comments and questions. After the latest release of this collection (5.4.0 and 6.1.0) the maintainers of this repository got pulled onto different projects and we were unable to review and merge anything for a little while. The recent CI fix unblocked several open PRs for the failing sanity tests, which is why it was the first thing to get merged. Your PRs as well as a few others will be reviewed before our next planned 5.5.0 and 6.2.0 releases. |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 27s |
Good to know that, thanks. Also for the update. I've also created a small PR with a fix to the integration test @ #981 |
I've pulled in the changes from main and pulled in my commit for this PR. |
Thanks again for this pull request, @yorick1989. Some thoughts after reviewing this PR: The k8s API's subresource design doesn't align well with the resource-oriented model that the rest of the k8s API fits into. Subresources are heterogeneous by nature (e.g., the scale subresource of deployments vs. the log and exec subresources of pods vs. the approval subresource of CSRs) and this heterogeneity requires specialized handling, which is why dedicated modules like Rather than adding generic subresource support to the main
Please let us know what you think of the above. |
Thank you for your reply. I'd agree with your comment. Do you think it's valuable to create a separate |
SUMMARY
Added the option
subresources
to thekubernetes.core.k8s
module, to support subresources.ISSUE TYPE
ADDITIONAL INFORMATION
Check below the test I ran by approving a CSR by using the 'approval' subresource of the 'certificatesigningrequest' resource.
Added the CSR
Output
Pull the CSR info
Output
Approve the CSR
Output
Double-check, using the
oc
commandPlease, let me know if there is more required for this to be implemented.
Thanks!