Repository navigation
Name the AWS root-volume scan om scan workload aws - #125
Merged
Merged
Conversation
Azure and GCP already name the cloud, and the bare command was running the AWS scan. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
om scan workloadis a group command and does not run a scan.om scan workload aws, next toom scan workload azureandom scan workload gcp.Test plan
om scan workloadprints the three cloud commands and does not start a scanom scan workload aws --helplists the EC2 IAM actions and the--instanceflagom scan workload azure --helpandom scan workload gcp --helpstill describe those scansMade with Cursor