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

💡 Feature Request - Provide steps to evaluate for 'cannot-be-validated-with-arg' items #222

Open
terrymandin opened this issue Jun 19, 2024 · 1 comment
Labels
Enhancement 🆕 New feature or request Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities

Comments

@terrymandin
Copy link

Describe the solution you'd like

Updating the manual steps for the "ImpactedResources" tab on the WARA Action Plan spreadsheet can be quite time consuming. I appreciate that there are links provided in the APRL site, but with 3,600 manual tests to validate for my WARA, going through the links to find how to validate is going to be quite consuming. I recommend that we add the manual validation steps for each of the 'cannot-be-validated-with-arg' APRL items.

Describe alternatives you've considered

Only option I know of is to review the APRL links

Additional context

For example, look at this Restrict default access to Azure NetApp Files volumes. Doing this for all the manual checks is going to take me a long time.

@ejhenry ejhenry added the Enhancement 🆕 New feature or request label Jun 20, 2024
@oZakari oZakari added the Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities label Jun 20, 2024
@oZakari
Copy link
Collaborator

oZakari commented Jun 20, 2024

Hi @terrymandin, thanks for bringing this up. We are currently discussing potential options for this. However, as we currently have other high priority items, we don't have an anticipated ETA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement 🆕 New feature or request Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities
Projects
None yet
Development

No branches or pull requests

3 participants