-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
The module has a SERVER-94 loading issue #226
Comments
👍 |
In general, are custom parent properties/parameters considered evil? |
Not that I know of. Things loaded into global Ruby-space just have to be treated with care per my blog post. |
If you disregard the environment bleeding issue, the parent properties look elegant. By the time you go all meta-programming to make them environment safe, perhaps not so elegant anymore. |
This parent property was only used in one type for one parameter. Moving the validation to the type fixes environment bleed caused by loading pure ruby code like this. Fixes voxpupuli#226
This parent property was only used in one type for one parameter. Moving the validation to the type fixes environment bleed caused by loading pure ruby code like this. Fixes voxpupuli#226
This parent property was only used in one type for one parameter. Moving the validation to the type fixes environment bleed caused by loading pure ruby code like this. Fixes voxpupuli#226
The
firewalld
code has a SERVER-94 environment loading issue due to adding code to thePuppetX
global module space in Ruby.I have a guide on mitigating this posted at https://www.onyxpoint.com/fixing-the-client-side-of-multi-tenancy-in-the-puppet-server/.
Since this is simply code loaded in the Type, it may be simpler to move it into the Type namespace itself.
As it stands, any use of the existing code in multiple environments may result in unreliable behavior if the code in the
PuppetX
space is ever modified.The text was updated successfully, but these errors were encountered: