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

Subject: ResourceGroup and Resource scopes disappeared from azure_role_assignment #866

Open
victordetoni opened this issue Jan 30, 2025 · 6 comments · May be fixed by #868
Open

Subject: ResourceGroup and Resource scopes disappeared from azure_role_assignment #866

victordetoni opened this issue Jan 30, 2025 · 6 comments · May be fixed by #868
Assignees
Labels
bug Something isn't working

Comments

@victordetoni
Copy link

victordetoni commented Jan 30, 2025

Hello,

I've identified an issue with the Azure role assignments query in Steampipe. The query is no longer returning permissions set at the Resource Groups or Resources level.

To reproduce the issue, I ran the following query to check for any scopes containing resource groups or resources:

select scope from azure_all.azure_role_assignment
where scope like '%resourcegroups%' -- testando com letra minúscula
   or scope like '%ResourceGroups%'
   or scope like '%resource%';
+-------+
| scope |
+-------+
+-------+

Thanks
Victor

@victordetoni victordetoni added the bug Something isn't working label Jan 30, 2025
@victordetoni victordetoni changed the title ResouceGroup and Resource disapeard from azure_role_assignment Subject: ResourceGroup and Resource scopes disappeared from azure_role_assignment Jan 30, 2025
@pskrbasu pskrbasu transferred this issue from turbot/steampipe Feb 3, 2025
@ParthaI ParthaI self-assigned this Feb 3, 2025
@cbruno10
Copy link
Contributor

cbruno10 commented Feb 5, 2025

Hi @victordetoni , were those permission sets returned before? If so, do you recall around which version of the plugin you were seeing the correct results?

Also, sometimes Azure returns inconsistent casing in their API response data, if you try a case insensitive match:

select scope from azure_all.azure_role_assignment
where scope ilike '%resourcegroups%' -- testando com letra minúscula
   or scope ilike '%ResourceGroups%'
   or scope ilike '%resource%';

Do you see any of the expected scopes?

@victordetoni
Copy link
Author

Hi @cbruno10 thank you for your answer. I just tried your suggestion, but the problem persists:

Welcome to Steampipe v0.21.7
For more information, type .help
> select scope from azure_all.azure_role_assignment
where scope ilike '%resourcegroups%' -- testando com letra minúscula
   or scope ilike '%ResourceGroups%'
   or scope ilike '%resource%';
+-------+
| scope |
+-------+
+-------+

I have owner and global administrator permissions and I have been running this select for a year and this problem starts now.

@ParthaI
Copy link
Contributor

ParthaI commented Feb 7, 2025

Hi @victordetoni,

Apologies for the issue you're facing. I have raised a PR to address it. Hopefully, this will resolve the issue.

Thanks!

@victordetoni
Copy link
Author

Hi @victordetoni,

Apologies for the issue you're facing. I have raised a PR to address it. Hopefully, this will resolve the issue.

Thanks!

Thank you @ParthaI How can I find out when I can update this to use?

@ParthaI
Copy link
Contributor

ParthaI commented Feb 7, 2025

Hey @victordetoni,

The PR is currently under review, and I don’t have an exact ETA for the next release. However, this fix will definitely be included in the upcoming release version.

If you’d like to use the fix before the official release, you can build the plugin from the PR branch locally. Here’s how:

  1. Clone the repository: git clone https://github.com/turbot/steampipe-plugin-azure.git
  2. Navigate to the project directory: cd steampipe-plugin-azure
  3. Checkout the PR branch: git checkout issue-866
  4. Build the plugin by running thee command make
  5. Run your queries.

Thanks!

@victordetoni
Copy link
Author

Hey @victordetoni,

The PR is currently under review, and I don’t have an exact ETA for the next release. However, this fix will definitely be included in the upcoming release version.

If you’d like to use the fix before the official release, you can build the plugin from the PR branch locally. Here’s how:

  1. Clone the repository: git clone https://github.com/turbot/steampipe-plugin-azure.git
  2. Navigate to the project directory: cd steampipe-plugin-azure
  3. Checkout the PR branch: git checkout issue-866
  4. Build the plugin by running thee command make
  5. Run your queries.

Thanks!

Hi @ParthaI thank you! It worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants