You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using AmazonLinux 2 on Puppet nodes I want to use this module. That used to work before PR 667.
Describe the Solution You Would Like
If os.family is RedHat, but name is Amazon then skip the version requirement.
Describe Alternatives You've Considered
The current solution is to use 3.12.1, which makes us miss out on improvements.
Additional Context
AmazonLinux 2 is REHL 7 and thus has the os.family fact set to RedHat. Since the release version numbers describe the OS version it's in our AMI set to 2.2 which triggers a version check error.
The text was updated successfully, but these errors were encountered:
Any update on this? Appears that everything else works for us using docker_compose we just have to comment out that fail condition. Tried overriding using the acknowledge_unsupported_os = true to also bypass it but gets caught on line #488 in the init.pp file
Made #788 to make the acknowledge_unsupported_os setting allow Amazon Linux 2. Allows us to use the module there even though it's not officially supported yet.
This issue has been marked as stale because it has been open for a while and has had no recent activity. If this issue is still important to you please drop a comment below and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days.
Use Case
I'm using AmazonLinux 2 on Puppet nodes I want to use this module. That used to work before PR 667.
Describe the Solution You Would Like
If os.family is RedHat, but name is Amazon then skip the version requirement.
Describe Alternatives You've Considered
The current solution is to use 3.12.1, which makes us miss out on improvements.
Additional Context
AmazonLinux 2 is REHL 7 and thus has the os.family fact set to RedHat. Since the release version numbers describe the OS version it's in our AMI set to 2.2 which triggers a version check error.
The text was updated successfully, but these errors were encountered: