Good day,

Does puppet have a way of setting up provider dependencies before
setting up the provider itself?

Here's the scenario I'm trying to get working: I have some machines
that need to be database servers. I also have a mysql type/provider
that manages users and databases.

However, the provider only works if mysql is already installed, since
it requires '/usr/bin/mysql' to be present and fails the suitability
test if the binary is missing. Thus, I cannot install mysql and then
configure it -- I must install it by hand or using a class that does
the installation without any configuration and then change classes
once it is installed.

I have tried using "optional_commands" instead of "commands" in the
provider code. This allows the provider to be used, but it fails when
it tries to test or create resources because the command binaries are
apparently resolved at startup.

I had a hack in place that would pretend to configure mysql using fake
commands, which lets me set up the database as a two-step operation.
However, this requires additional code to test for the existence of
mysql around every further operation that requires the database to be
present.

The best solution I can see at the moment is to rewrite the provider
to do everything manually instead of using the built-in command
infrastructure. Are there any other options?

Thanks,
--J

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to