Skip to content

1509: fix ssl for debian Mariadb #1512

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

Closed
wants to merge 1 commit into from
Closed

Conversation

elfranne
Copy link
Contributor

#1511 is a fix for EL7, same fix for Debian

@elfranne elfranne requested a review from a team as a code owner November 24, 2022 12:38
@puppet-community-rangefinder
Copy link

mysql::params is a class

Breaking changes to this file WILL impact these 2 modules (exact match):
Breaking changes to this file MAY impact these 1 modules (near match):

This module is declared in 140 of 580 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@elfranne elfranne changed the title 1509: fix ssl for debian 1509: fix ssl for debian Mariadb Nov 24, 2022
@markruys
Copy link

A workaround is to add ssl-disable: true to your config. Although then you must live with:

Notice: /Stage[main]/Mysql::Server/Notify[ssl-disable]/message: current_value 'absent', should be "Disabling SSL is evil! You should never ever do this except\n
                if you are forced to use a mysql version compiled without SSL support" (noop)

Seriously? Module maintainers, please remove this silly repeating message. We're not kids, so let us be responsible for our own acts :)

@chelnak
Copy link
Contributor

chelnak commented Dec 5, 2022

@markruys Hi! We would welcome a PR if you'd like to change the presentation of this message.

Alternatively you can open a new issue and ask for its removal.

Thanks,
Craig

@LukasAud
Copy link
Contributor

Hi @elfranne, this issue has already been addressed in the following PR. If the issue still persists for you despite this update, please let us know. Otherwise, this PR can be closed.

@elfranne elfranne closed this Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants