Skip to content

Conversation

@kmcquade
Copy link
Collaborator

@kmcquade kmcquade commented Feb 8, 2022

What does this PR do?

What gif best describes this PR or how it makes you feel?

image

Completion checklist

  • Additions and changes have unit tests
  • The pull request has been appropriately labeled using the provided PR labels
  • GitHub actions automation is passing (make test, make lint, make security-test, make test-js)
  • If the UI contents or JavaScript files have been modified, generate a new example report:
# Generate the updated Javascript bundle
make build-js

# Generate the example report
make generate-report

… to flag risky actions regardless of resource constraints or conditions usage
@kmcquade kmcquade added the DO-NOT-MERGE Don't merge yet label Feb 8, 2022
… to flag risky actions regardless of resource constraints or conditions usage
…ctions regardless of resource constraints or conditions usage.
@kmcquade kmcquade removed the DO-NOT-MERGE Don't merge yet label Feb 8, 2022
@kmcquade kmcquade changed the title WIP: Initial modifications to address #254 - allow noisy results to flag risky actions regardless of resource constraints or conditions usage Optionally allow noisy results to flag risky actions regardless of resource constraints or conditions usage Feb 8, 2022
@kmcquade kmcquade merged commit 3381965 into salesforce:master Feb 9, 2022
@kmcquade kmcquade deleted the fix/GH-254-flag-all-risky-actions branch February 9, 2022 20:05
leonamagaya pushed a commit to leonamagaya/cloudsplaining that referenced this pull request Aug 19, 2025
…source constraints or conditions usage (salesforce#257)

Add --flag-all-risky-actions to arguments for scan and scan-policy-file commands
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide option to flag all risky actions, regardless of resource constraints or conditions

1 participant