-
-
Notifications
You must be signed in to change notification settings - Fork 505
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
💥 Update ALL remaining roles to new format (with docs and tests) #655
Conversation
freshrss, get_iplayer, gitlab, glances, gotify, guacamole, healthchecks.io
Wow, this is amazing, thank you! I'll start reviewing this week, hopefully won't take too long to get merged. |
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.
This looks great, thank you for taking the time!
Few comments;
- all of the doc moves have been dragged and dropped rather than
git mv ....
, which means the files are showing as new additions, and we lose the history. - the roles I'd already rejigged are missing the new docker settings - these are a nice addition so would be good to add
- the docs generation doesn't currently cater for docs within the role directories, so will need some shell scripting to set up (or the docs be left in their original location for now).
Do you mean moves of existing docs from
Which setting do you mean exactly?
Yes, so the docs are left in their original settings (when I add new roles for myself I add docs to both locations for now), and in new roles location - just to be consistent with |
Ok, I think it should be rather |
…/freshrss/docs/ history.
…y in roles/gitea/docs/ history.
…ry in roles/gitlab/ history.
…roles/glances/docs/ history.
…gotify/docs/ history.
…es/guacamole/docs/ history.
…istory in roles/healthchecks.io/docs/ history.
… roles/heimdall/docs/ history.
…in roles/sonarr/docs/ history.
…n roles/speedtest-tracker/docs/ history.
…les/stats/docs/ history.
… in roles/syncthing/docs/ history.
… in roles/tautulli/docs/ history.
…es/thelounge/docs/ history.
…history in roles/tiddlywiki/docs/ history.
…ry in roles/timemachine/docs/ history.
…/traefik/docs/ history.
…story in roles/transmission/docs/ history.
…story in roles/transmission-with-openvpn/docs/ history.
…y in roles/ubooquity/docs/ history.
…y in roles/utorrent/docs/ history.
…in roles/virtual_desktop/docs/ history.
…s/wallabag/docs/ history.
…y in roles/watchtower/docs/ history.
…n roles/wireshark/docs/ history.
…d history in roles/woodpecker-ci/docs/ history.
…md history in roles/youtubedlmaterial/docs/ history.
Well, I copied the files using git-cp which was supposed to copy git history, but I don't see that git history :/ |
Ah, that makes sense why they are showing as new files. I think it'll end up as a management nightmare having two copies of the docs - so please can we remove the new copies and leave the docs where they were originally. Once I get to sorting out the docs generation I can move them into the roles again! |
Ok, I removed the new/individual docs, and also rebased to upstream |
Finally got this one merged - thanks for your efforts - I also did a fair bit of extra work on it :) Also - the following tests aren't passing:
It seems that they are all roles that have been flipped to creating a network over the legacy |
Thanks! Yes, I fillpped them over to the new method over deprecated link method. |
Interestingly they pass on GitHub, but fail locally. I'll do some more
digging!
…On Wed, 19 Apr 2023, 07:22 Anarion, ***@***.***> wrote:
Thanks! Yes, I fillpped them over to the new method over deprecated link
method.
I quickly checked the first two roles on new_format branch and they are
passing tests all right.
I will rebase my master and check there.
—
Reply to this email directly, view it on GitHub
<#655 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFDGMEC4RGGB2VZS4TFGXDXB6AAXANCNFSM6AAAAAAVXP5TF4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
What this PR does / why we need it:
As in the title: I updated all the remaining roles to new format - adding docs and molecule tests. I know this doesn't really adhere to your contributing guideline, but you're probably busy, PR intake is slow, so here it is.
While creating passing tests I had to fix some roles:
From the general things:
All passing tests are here: https://github.com/anarion80/ansible-nas/actions/runs/4392401003
Which issue (if any) this PR fixes:
Fixes #
Any other useful info: