Need guidance on next steps after CloudQuery issue moved to ready state

CloudQuery Plugins
1

Hi team,

I have raised an issue in CloudQuery and also suggested a fix. It has been moved to the ready state by Erezrokah.

I am not sure what to do next; can anyone help me?

2

Hi,

Thanks for opening the issue and suggesting the fix! Our team will probably get to it next week and open a PR. If you need it urgently, you can fix it in your branch or alternatively open a PR and if all tests pass, I can merge it.

3

Hey @yevgenyp,

I have raised the PR: 14195.
Could you clarify what the use of wait-for-required-workflows is? This check keeps running for so long after all the other checks have passed.

4

Hey @closing-duckling - thanks for the contribution! We reviewed the PR and merged it in as well as closed the issue.

In short, the fix you submitted will resolve the false positives where Storage Accounts are set to allow public Blob Storage but Containers are set to not allow public access (None). However, I believe the logic will need to be checked for classic storage accounts that may behave differently. We’ll take a look at classic storage accounts at a later date.

Thanks again!