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.

Sign up for GitHub

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

Jump to bottom

Backporting a chef-18 fix for sensitive properties #13817

Merged
merged 1 commit into from Jun 23, 2023
Merged

Backporting a chef-18 fix for sensitive properties #13817

merged 1 commit into from Jun 23, 2023

Conversation

johnmccrae
Copy link
Contributor

Description

Backporting this PR #13014 to chef-17

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

@johnmccrae
Backporting a chef-18 fix for sensitive properties
5ca4fd4 
Signed-off-by: John <john.mccrae@progress.com>
@johnmccrae johnmccrae requested review from a team as code owners June 22, 2023 15:32
@sonarcloud
Copy link

sonarcloud bot commented Jun 22, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@johnmccrae johnmccrae merged commit 251c28d into chef-17 Jun 23, 2023
27 of 33 checks passed
@johnmccrae johnmccrae deleted the jfm/chef17-sensitive_keyword branch June 23, 2023 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tpowell-progress tpowell-progress tpowell-progress approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@johnmccrae @tpowell-progress