Skip to content
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

Drop support for Puppet 4, 5, 6 (EOL) #101

Merged
merged 15 commits into from
Sep 10, 2024
Merged

Drop support for Puppet 4, 5, 6 (EOL) #101

merged 15 commits into from
Sep 10, 2024

Conversation

smortex
Copy link
Member

@smortex smortex commented Aug 20, 2024

bastelfreak and others added 15 commits June 21, 2024 10:24
These corrections are always safe:

bundle exec rubocop -a
These ones are sometimes not safe

bundle exec rubocop -A
The list of supported Operating Systems is outdated.  Update it and add
some basic acceptance tests to ensure the code is valid.
While AIO Puppet has a well-known path to augeas lenses, non-AIO Puppet
use a sysstem path that is OS-dependant.

Rework the way this path is retrieved so that we can extand this easily
using Hiera.
Puppet 7 and Puppet 8 are the currently supported versions of Puppet.
Older versions have reached EOL and are not used in CI, so do not
pretend the module work with them as it is now untested.
@smortex smortex added the backwards-incompatible This change will lead to a major version bump for the next release label Aug 20, 2024
@smortex
Copy link
Member Author

smortex commented Aug 20, 2024

Interesting, in facterdb, Archlinux (and a bunch of other OS) does not have a puppetversion fact.

@jhoblitt
Copy link
Member

I'd rather the individual PRs aggregated here are merged separately so they appear in the change-log.

@kenyon
Copy link
Member

kenyon commented Aug 22, 2024

@jhoblitt they'll all appear in the changelog when closed, regardless of how they are merged.

Copy link
Member

@jhoblitt jhoblitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a lot going on this PR that I feel would be better merged as isolated PRs that appear in the changelog. Also, some of the commits in this branch have a lot going on in them that isn't reflected in the commit messages. E.g. f6974ed

The PR title here also won't be very helpful in the changelog. What versions of puppet is support being dropped for?

I suggest starting with a small PR that only removes the EOL puppet versions.

@jhoblitt
Copy link
Member

@jhoblitt they'll all appear in the changelog when closed, regardless of how they are merged.

Closed but unmerged PRs do not appear in the changelog.

@kenyon
Copy link
Member

kenyon commented Aug 22, 2024

@jhoblitt they'll all appear in the changelog when closed, regardless of how they are merged.

Closed but unmerged PRs do not appear in the changelog.

When this PR is merged, the included ones will also be closed as merged.

@kenyon
Copy link
Member

kenyon commented Aug 22, 2024

There is a lot going on this PR that I feel would be better merged as isolated PRs that appear in the changelog. Also, some of the commits in this branch have a lot going on in them that isn't reflected in the commit messages. E.g. f6974ed

AFAICT, in that commit, all of the deleted code was only applicable to EOL versions of Puppet, where Augeas was not included in the all-in-one packages like we have now.

@smortex smortex changed the title Drop support for EOL Puppet Drop support for Puppet 4, 5, 6 (EOL) Aug 23, 2024
@smortex
Copy link
Member Author

smortex commented Aug 23, 2024

The PR title here also won't be very helpful in the changelog. What versions of puppet is support being dropped for?

👍 Fixed, thanks!

When this PR is merged, the included ones will also be closed as merged.

That's correct, when all commits in a PR are merged, the PR is marked as merged and GitHub ChangeLog Generator include it as expected.

AFAICT, in that commit, all of the deleted code was only applicable to EOL versions of Puppet, where Augeas was not included in the all-in-one packages like we have now.

Correct, and we also discover that the legacy code was used on some platforms because they do not ship with puppetversion?!

@jhoblitt
Copy link
Member

jhoblitt commented Sep 9, 2024

Could we either accept the arch failure and merge this or remove arch from this PR? We need to get a forge release out.

@smortex
Copy link
Member Author

smortex commented Sep 10, 2024

Could we either accept the arch failure and merge this or remove arch from this PR? We need to get a forge release out.

@bastelfreak you are my Arch referent :-D What do you think we should do?

@bastelfreak
Copy link
Member

The Arch Linux failure was an actual bug. the puppet package didn't depend on ruby-augeas. I fixed the package upstream.

@bastelfreak bastelfreak merged commit 98d2a42 into master Sep 10, 2024
11 checks passed
@bastelfreak bastelfreak deleted the drop-eol-puppet branch September 10, 2024 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backwards-incompatible This change will lead to a major version bump for the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants