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

Issue with Authorization / Role Management Policies / API Version 2020-10-01 #287

Closed
1 task done
josh-barker opened this issue Feb 6, 2023 · 0 comments · Fixed by hashicorp/pandora#2869
Closed
1 task done
Assignees

Comments

@josh-barker
Copy link

josh-barker commented Feb 6, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Service Used

Authorization / Role Management Policies

API Versions Used

2020-10-01

Description

Hi, I'm working on a new AzureRM Terraform resource - azurerm_role_management_policy.

I'm trying to access the data inside a Rule.

However, the RoleManagementPolicyRule is an empty interface.
The rule is created as RawRoleManagementPolicyRuleImpl and it is a private struct.

My current workaround is to move the RawRoleManagementPolicyRuleImpl struct outside of the. unmarshalRoleManagementPolicyRuleImplementation function so that it's public.

FYI: @manicminer

References

No response

@josh-barker josh-barker changed the title Issue with Authorization / API Version 2020-10-01 Issue with Authorization / Role Management Policies / API Version 2020-10-01 Feb 6, 2023
@tombuildsstuff tombuildsstuff self-assigned this Aug 1, 2023
tombuildsstuff added a commit to hashicorp/pandora that referenced this issue Aug 1, 2023
This PR fixes hashicorp/go-azure-sdk#287 by exposing
the Raw types rather than using internal types for these.

Since these fields are intentionally only consumable via the Response and are not usable in Request Payloads
exposing this is reasonable, but I've added a warning that these should be a last resort/workaround only.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants