-
Notifications
You must be signed in to change notification settings - Fork 21
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
Review pages where ansible_ssh_user is still in use #251
Comments
Should I re-work the pages one by one? I'll happily do it, up to you :-) |
Related to: debops/docs#251
I added the substitution to |
Did this one right now: https://github.com/debops/ansible-atd/pull/9 How do I ask? @ypid makes me a list and work on that or I follow this: Search: https://docs.debops.org/en/latest/search.html?q=ansible_ssh_user&check_keywords=yes&area=default |
https://docs.debops.org/en/latest/search.html?q=ansible_ssh_user&check_keywords=yes&area=default should be ok for this case when you only want to update the variable. I am just not sure if the DebOps Developers could not do this more conveniently when reworking roles anyway. Ideally you would search for all occurances of |
OK, I'll go for your proposal, docs and code + min_ansible_version: '1.9.0' -> min_ansible_version: '2.0' + if needed - name: Debian versions: - wheezy - jessie add - stretch. - Or do I forget about stretch for the moment? |
When you have tested that the role actually works with stretch why not. I would not just add it just for the sake of it :) |
True, so I'll leave it in the future (one is already done without testing on stretch) without stretch. |
Looks good to me. But keep in mind that you can automate most of the work when you want to get a little fancy :) Still some changelog stuff and other things might have to be done manually. I thought for a sec that we deprecated |
I'm pretty sure you as a hacker/coder can automate this replacement work. :-) - But not me as Joe Average or a simple supporter. I would spend much more time for automation, than update 25 files. :-(
|
All right.
Deprecated disappear from the status page currently. I think there is an issue for status field. It has been requested a number of times but I am not really convinced :) |
Maybe at the end of the status page, there could be a section Anyhow, for the moment being, I'm not aware of any deprecated role in DebOps. |
Lets just say I am not convinced that this should be on my todo right now :) There are some. |
Don't worry, I don't wanna convince you of anything :) Then following your Still listed in the DebOps status page. Both roles with Warning, this is a deprecated role It has been superseded by blabla. - So far fine and correct. What's for me a bit uncool, is the statement at the beginning of the status page:
What is somehow not true, as two of the 122 are deprecated. And as a newbie to DebOps, clicking by chance on the debops/ansible-mysql and then reading the warning, you feel very likely somehow mucked. |
@drybjed I guess those roles should be removed from debops/docs? |
Or at least removed from the status page; as long there is no column (Deprecated y/n) or section "Deprecated roles" at the end of the status page. The latter, at the end of the page, I would prefer, as it doesn't blow up the role table. Both might make sense, as documentation of such circumstances might be asked by Best Practice Badge of CII. But I'm not sure about that. |
Removing from debops/docs will also remove them from the status page. |
Hmmm... what is your suggestion then? I mean, above you asked (and I supported)
|
Removing from both for now. They can still be found on GitHub. |
If we do so, I suggest to open an issue "Status page / Deprecated rolls" in github debops/docs as a reminder. Including layout of (far in the) future "status page". Status page |
Since Ansible 2.0 and higher where
ansible_ssh_user
is deprecated and replaced byansible_user
[tallandtree_]Search: https://docs.debops.org/en/latest/search.html?q=ansible_ssh_user&check_keywords=yes&area=default
The text was updated successfully, but these errors were encountered: