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

group: convert to properties with descriptions and improve comma separated parsing #7474

Merged
merged 5 commits into from Jul 17, 2018

Conversation

tas50
Copy link
Contributor

@tas50 tas50 commented Jul 16, 2018

This converts another resource to use properties and gives each property
a description from the docs site.

It also makes the string parsing a bit more user spacing proof.

accepted before:

  • 1,2,3

accepted now:

  • 1,2,3
  • 1, 2, 3
  • 1 ,2 ,3
  • any combo of the above 3

Signed-off-by: Tim Smith tsmith@chef.io

This converts another resource to use properties and gives each property
a description from the docs site.

Signed-off-by: Tim Smith <tsmith@chef.io>
@tas50 tas50 requested a review from a team July 16, 2018 18:27
This is ancient and we don't have to worry about it.

Signed-off-by: Tim Smith <tsmith@chef.io>
We're trying to catch everything linux here. Just catch that.

Signed-off-by: Tim Smith <tsmith@chef.io>
These can't be directly set to nil anymore.

Signed-off-by: Tim Smith <tsmith@chef.io>
This is the same thing I did in sudo. It just makes the string parsing a bit more user spacing proof.

accepted before:
  - 1,2,3

accepted now:
  - 1,2,3
  - 1, 2, 3
  - 1 ,2 ,3
  - any combo of the above 3

Signed-off-by: Tim Smith <tsmith@chef.io>
@tas50 tas50 changed the title Convert group resource to use properties with descriptions group: convert to properties with descriptions and improve comma separated parsing Jul 17, 2018
@tas50 tas50 merged commit 913da4c into master Jul 17, 2018
@tas50 tas50 deleted the group_properties branch July 17, 2018 21:50
@lock
Copy link

lock bot commented Sep 15, 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 Sep 15, 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

Successfully merging this pull request may close these issues.

None yet

2 participants