Ask Your Question
0

Custom provider: How to refetch a resource after its creation?

asked 2015-01-23 11:39:13 -0500

Arney gravatar image

In my custom provider I'd like to keep the create method very lean.

I would like to just create the resource on the system, and then have Puppet run the getters and (where needed) the setters on it. I.e. I want Puppet to do immediately, what would happen in a second Puppet run.

Can it be done?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2015-01-25 17:38:06 -0500

Stefan gravatar image

I don't think I get your point. If you just created the resource inside your create method, you should already now the status of the resource - you created it.

In general puppet syncs all properties, which means it will run the getter and setter commands for each property. One exception to that rule (as you noticed) is the ensure property which will always be the first one to be checked (by running the exists? method of your provider). If this is out of sync (the resource is absent but you want it to be present / the resource is present but you want it to be absent) the create/destroy method of your provider is executed and nothing else. Puppet will just expect that if you destroyed a resource there is no point in checking any remaining properties and if you just created a resource, you'll create the resource in the desired state right away.

If you take the user provider for example: To create a user you should run useradd in a way that uid, gid, groups etc are already set up correctly and there is no point to run any usermod afterwards.

There are only a few exceptions to the rule that don't fit into this pattern and the mount type comes to mind. Here a change form unmounted to mounted is realized by running mount /foo, but this does not fix any incorrect entries in /etc/fstab. So inside the mount type you will find a really ugly hack that syncs all other properties from within the ensure property. That's not a good idea and probably means your ensure property is bad designed.

Can you point us to some sample code or at least explain what your custom type is about?

edit flag offensive delete link more

Comments

As we already implemented the property setters, why implement them yet another time in `create`? `create` could just create the user and then automagically call all setters necessary. At least, that's what I pictured to be standard procedure.

Arney gravatar imageArney ( 2015-03-24 10:11:49 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2015-01-23 11:39:13 -0500

Seen: 147 times

Last updated: Jan 25 '15