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

Find how to call updated_by_last_action on nested resources #12

Closed
brianbianco opened this issue Jul 15, 2012 · 3 comments
Closed

Find how to call updated_by_last_action on nested resources #12

brianbianco opened this issue Jul 15, 2012 · 3 comments

Comments

@brianbianco
Copy link
Contributor

See if it is possible to pass on the updated_by_last_action from resources called within a provider. WIthout doing that it will be pretty difficult to properly called updated_by_last_action for the configure step of the redisio install provider. This is a shame because it would be nice to provide the option to allow for the LWRP to use notifications for restarts.

@brianbianco
Copy link
Contributor Author

I've actually got a pattern now that does this. It is implemented in the install resource. I'll have to go through the other providers and see if they need to use it as well. It might be nice to clean up the usage of the new_resource attr and store the actual object in a variable instead of praying that the proper run_context is set in nested resources.

@brianbianco
Copy link
Contributor Author

This has been implemented as a method living in the RedisioHelper module. I tested it and it works.

@lock
Copy link

lock bot commented Nov 28, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant