fix(misconf): correctly adapt storage account network rules

[nikpivkin]

If there are no network rules in the Storage Account configuration, adaptation results in the use of incorrect metadata without location.

Discussed in #9059

[AngryCatKR96]

Hi! I was the original reporter of this issue via discussion #9059.

I appreciate the quick fix, but I was hoping to contribute by working on this
myself since I did the initial analysis. For future similar cases,
it would be great if there could be a brief check with the original reporter
before implementing - just to see if they're interested in contributing.

Could I get credit as the issue reporter? And I'd love to work on other issues too!

[simar7]

Hi! I was the original reporter of this issue via discussion #9059.

I appreciate the quick fix, but I was hoping to contribute by working on this myself since I did the initial analysis. For future similar cases, it would be great if there could be a brief check with the original reporter before implementing - just to see if they're interested in contributing.

Could I get credit as the issue reporter? And I'd love to work on other issues too!

hi @AngryCatKR96 - while we appreciate your interest in Trivy, we don't implement any mechanism to assign tasks for outside contributors. If you'd like to contribute next time, feel free to start a discussion first and accordingly create a PR to tackle it.

[AngryCatKR96]

Hi! I was the original reporter of this issue via discussion #9059.
I appreciate the quick fix, but I was hoping to contribute by working on this myself since I did the initial analysis. For future similar cases, it would be great if there could be a brief check with the original reporter before implementing - just to see if they're interested in contributing.
Could I get credit as the issue reporter? And I'd love to work on other issues too!

hi @AngryCatKR96 - while we appreciate your interest in Trivy, we don't implement any mechanism to assign tasks for outside contributors. If you'd like to contribute next time, feel free to start a discussion first and accordingly create a PR to tackle it.

I think there might be some confusion - I actually did start the discussion first (#9059), which led to this issue being created.

According to the docs, it says minor changes can go directly to PR.

If you think your change is trivial enough, you can skip the issue and instead add justification and explanation in the PR description.

But I thought the general process is discussion → issue → PR since issues created by non-maintainers are automatically deleted. So I was waiting for a maintainer to create the issue (as happened here) before proceeding with a PR.

My feedback was about giving original reporters a chance to contribute before maintainers implement the fix themselves, especially when they've already done the analysis and expressed interest in working on it.

I understand there's no formal assignment mechanism, but a brief check with the original reporter could help encourage more contributions to the project. Please note that I have no intention of being aggressive - just hoping to provide constructive feedback for future cases.

Thank you for maintaining this great project!

[nikpivkin]

Hi @AngryCatKR96 !

Thank you for the feedback! We truly encourage and welcome contributions from issue reporters. However, sometimes it’s difficult to assess the root cause of a problem at first glance, which requires further investigation and a good understanding of the codebase. This can take considerable time for community members, whereas maintainers often resolve it more quickly.

Thanks again for your engagement and support!