[infra-proxy-service]Removed validation for description field while update role. #5648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Himanshi Chhabra hchhabra@progress.com
🔩 Description: What code changed, and why?
Update Role even if the description field is blank.
⛓️ Related Resources
#5317
👍 Definition of Done
Updated Role even if the description field is blank.
👟 How to Build and Test the Change
Steps to build:
Steps to test:
start_chef_server
knife create role test1
test1
role -> edit runlist or attribute and updating successfully if description is null.✅ Checklist
All PRs must tick these:
With occasional exceptions, all PRs from Progress employees must tick these:
make spell
in any component directory)All PRs from Progress employees should tick these if appropriate:
Please add a note next to any checkbox above if you are NOT ticking it.
📷 Screenshots, if applicable
description-val.mp4