-
Notifications
You must be signed in to change notification settings - Fork 16
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
Expose full path to resource #14
Conversation
lockfile changes aren't related to my change - but I bumped them in a separate commit to capture the recent greenkeeper bumps that didn't check in the associated lockfile changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice change
Oops! Forgot docs. Added. |
@@ -121,9 +121,9 @@ The output is an object with these top-level properties: | |||
Each _changed resource_ has the following properties: | |||
|
|||
- **`action`:** One of `"create"`, `"destroy"`, `"replace"`, `"update"` | |||
- **`module`:** Name of a module that contains a resource (only present when module is not `root`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleted since this is a duplicate description, and the other description is better IMO.
Published |
E.g.
Exposing the
path
is very convenient for consumers and it's already in memory/computed anyway. It avoids having to try and rebuild the path based on the module, name, (data) type, etc.