Skip to content
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

Disable node on rename? #14

Open
rojspencer opened this issue May 21, 2015 · 1 comment
Open

Disable node on rename? #14

rojspencer opened this issue May 21, 2015 · 1 comment

Comments

@rojspencer
Copy link

Wondering if it's possible to have this plugin disable a node when it's renamed in Foreman (its old name). Sort of on the line of the DHCP, DNS functionalities that update the other services after a host is renamed.

Recently had an issue where a number of physical hosts were renamed in Foreman and then rebuilt. PuppetDB still held the old names along with all their exports -- which didn't make our monitoring system (fed from puppet) happy trying to monitor 2 separate hosts with the same IP address.

@dLobatog
Copy link
Member

dLobatog commented Jun 5, 2015

I think that's reasonable, we can catch the event in an after_validation filter. I'm not sure I can get to it soon, but a patch would be appreciated and carefully reviewed 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants