-
Notifications
You must be signed in to change notification settings - Fork 95
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
Module does not allow the management on Amazon Linux #77
Comments
Just discovered this also. The AWS documentation about EPEL on EC2 instances states that Amazon linux ships with EPEL repo description which is disabled by default. The intention of this puppetmodule seems to be just to enable it (which makes sense) - I'm just not sure that Yumrepo resource works that way. |
Seems to work if the epel.repo definition is already installed. Perhaps newer Amazon Linux hosts don't have this. IDK. |
I use this module to configure the epel repo to point to an internal baseurl and it's works just fine. My issue is that I simply can't do the same configuration changes on Amazon. If the default behavior is just to enable the module on Amazon that's ok, I would just like the ability to override that default behavior. Maybe we add a switch/mechanism to allow this? |
I don't use much amazon linux. If there's a behavior change you desire, could you submit a PR? |
#95 should fix this behavior, @bdrust and @bramblek1 can you confirm this addresses your needs before we close the ticket? |
Closing this as some use cases may already be addressed, and #105 will add declared support (instead of best effort) but is dependent on external changes. |
When running on Amazon Linux the module only calls the yumrepo resource with the 'enabled' and 'gpgcheck' parameters. You are unable to configure anything else, is there a reason for this? I need to be able to set my baseurl, mirrorlist, and a few others on Amazon Linux instances.
The text was updated successfully, but these errors were encountered: