-
Notifications
You must be signed in to change notification settings - Fork 104
Check for missing commits vs devel #49
Comments
@gundalow - Just noting that this repo has also had some commits since it was forked out of |
Clarification:
|
Here's the output from a one-for-one diff of the two repos (from this repo): |
File-by-file breakdown:
All the other changes are inconsequential (e.g. test changes, fixes we've done in this repo to whittle down the sanity check |
For the missing file, that was a mistake on my part, I forgot to route |
Three fixes didn't make their way into this collection's code:
|
I'm going to try to get the rests of these fixes in today. |
I created the above three PRs with commits attributed to the original authors, once tests pass I'll merge them in order. It seems like they will not conflict in any way so it should just be a matter of waiting for all of them to pass. Note that #55 and #56 at least (not sure about #54) were slated for 2.10, so if we add the change to the 0.9.x release series it would be a feature addition that would likely wind up in Ansible 2.10/ACD. I'm okay with that as it doesn't seem to be a breaking change... but just wanted to point that out. The first ACD release could be a bit of a wild ride, at least for any modules that are actively maintained between now and it's release day... |
Those three PRs are in, but I'm going to have to pause the fixing of the rest of the minor changes (mostly taking out |
I'm not going to add |
Not going to touch the |
PR with final fixes for this issue: #59 |
Final fixes are in; other issues are broken out (and not blocking further releases of this collection), so I'm going to close this issue now. |
SUMMARY
The "Big Migration" has now taken place.
As this collection already exists, we need to carefully check to see if any further commits went into devel since this repo was created.
Please check the contents of https://github.com/ansible-collection-migration/community.kubernetes against this repo
ISSUE TYPE
The text was updated successfully, but these errors were encountered: