Skip to content
This repository has been archived by the owner on Jun 25, 2023. It is now read-only.

THIS ROLE IS DEPRECATED: Rationale & Alternatives #98

Closed
jnv opened this issue May 23, 2022 · 6 comments
Closed

THIS ROLE IS DEPRECATED: Rationale & Alternatives #98

jnv opened this issue May 23, 2022 · 6 comments

Comments

@jnv
Copy link
Owner

jnv commented May 23, 2022

Unfortunately I don't have time nor motivation to maintain this role anymore, so with this I announce that the jnv.unattended-upgrades role is deprecated.

This probably doesn't come as a surprise with multiple unanswered issues and pull requests. I originally hoped to finish the migration to v2.0 of this role with #32, but with the closure of Travis CI I have lost the testing setup. And since I don't use this role myself anymore (nor Ansible), I don't have any confidence in pushing changes to this role.

I appreciate all the time you spent with your contributions and I am sorry if your PR wasn't accepted.

What's next?

I have pushed one last update with link to this issue in the README and marked the role as deprecated in Galaxy.

I won't be accepting pull requests and bug reports, but I won't archive the repository to keep this issue open for comments.

I would like to collect alternatives and significant forks of this role in this issue. Please, comment with your recommendations – especially for roles with a migration path from this role!

Unresolved issues and pull requests

The following issues remain unresolved with this role:

Alternative roles

Check out the maintained fork of this role by @hifis-net: https://github.com/hifis-net/ansible-role-unattended-upgrades (hifis.unattended_upgrades on Galaxy).

Other roles with similar purpose (I haven't tested them, but they seem actively maintained and popular):

Further recommendations are welcome, especially if they provide a migration path from this role.

@jnv jnv pinned this issue May 23, 2022
@lonix1
Copy link

lonix1 commented May 23, 2022

Thanks for maintaining it up to now.

If you don't use Ansible any longer, what do you use?

@jnv
Copy link
Owner Author

jnv commented May 24, 2022

If you don't use Ansible any longer, what do you use?

I didn't move to greener pastures, I just don't manage servers anymore. 🙂

@lonix1
Copy link

lonix1 commented May 24, 2022

That sounds to me like moving to greener pastures! 😉

@Normo
Copy link

Normo commented Aug 16, 2022

Thank you very much @jnv!

As a HIFIS Software team member I'm happy to tell you that we already created a fork for this project. As we are actively using the role in our projects, we will continue the development and maintenance of this role. It is available in the Ansible Galaxy and can be installed via this command:

$ ansible-galaxy install hifis.unattended_upgrades

Feel free to open issues or pull requests!

@jnv
Copy link
Owner Author

jnv commented Aug 16, 2022

Thanks @Normo, that's great news! I have added it to the first post and linked it from the readme.

hemberger added a commit to hemberger/seed-server that referenced this issue Sep 23, 2022
The original version of this role has been deprecated in favor of one
of its forks.

See jnv/ansible-role-unattended-upgrades#98.
hemberger added a commit to smrealms/seed-server that referenced this issue Sep 23, 2022
The original version of this role has been deprecated in favor of one
of its forks.

See jnv/ansible-role-unattended-upgrades#98.
jkirk added a commit to jkirk/ansible-site-template that referenced this issue Sep 30, 2022
`jnv.unattended-upgrades` has been deprecated, see: jnv/ansible-role-unattended-upgrades#98

The author (@jnv) states:

> Unfortunately I don't have time nor motivation to maintain this role
> anymore, so with this I announce that the jnv.unattended-upgrades role
> is deprecated.

@hifis-net (Thx!) took over and maintains a fork of the ansible role
which is now called `hifis.unattended_upgrades`.

---

WIP: Currently the fork is [56 commits ahead](jnv/ansible-role-unattended-upgrades@master...hifis-net:ansible-role-unattended-upgrades:0f44252)

The commits till 0f44252 have been reviewed and look good so far.
We have to test a migration and if everything works out fine, merge this
to master.
@jnv
Copy link
Owner Author

jnv commented Jun 25, 2023

Since we have an official replacement now, I think it's time to archive this repo. So long, and thanks for all the fish!

@jnv jnv closed this as completed Jun 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants