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

Move to generic context variable instead of $Rule #341

Closed
BernieWhite opened this issue Dec 1, 2019 · 0 comments · Fixed by #342
Closed

Move to generic context variable instead of $Rule #341

BernieWhite opened this issue Dec 1, 2019 · 0 comments · Fixed by #342
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@BernieWhite
Copy link
Member

Originally the intent of the $Rule variable was to provide context about the current rule.

Over time $Rule has had additional properties added to it. Additional context properties and potentially helper methods will be required (i.e. #321). Based on this it makes sense to return $Rule to a pure rule context instead of a generic pipeline context.

An additional $PSRule context variable will be created to handle generic context information.

Existing TargetName, TargetType and TargetObject properties on $Rule should be deprecated in favor of $PSRule.

@BernieWhite BernieWhite added the enhancement New feature or request label Dec 1, 2019
@BernieWhite BernieWhite added this to the v0.12.0 milestone Dec 1, 2019
@BernieWhite BernieWhite self-assigned this Dec 1, 2019
BernieWhite added a commit that referenced this issue Dec 1, 2019
This was referenced Dec 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant