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

docs: Add explanation on User-Assigned Managed Identities in ALZ policies to FAQ #1874

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

jtracey93
Copy link
Collaborator

@jtracey93 jtracey93 commented Dec 20, 2024

This pull request adds a new FAQ section to the docs/wiki/ALZ-Policies-FAQ.md file. The new section addresses the reasons why ALZ does not promote the usage of User-Assigned Managed Identities for Policy Assignments.

Documentation updates:

  • docs/wiki/ALZ-Policies-FAQ.md: Added a new FAQ entry explaining the risks and reasons behind not promoting User-Assigned Managed Identities for Policy Assignments in ALZ.

As part of this Pull Request I have

  • Checked for duplicate Pull Requests
  • Associated it with relevant issues, for tracking and closure.
  • Ensured my code/branch is up-to-date with the latest changes in the main branch
  • Performed testing and provided evidence.
  • Ensured contribution guidance is followed.
  • Updated relevant and associated documentation.
  • Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)

@jtracey93 jtracey93 requested a review from a team as a code owner December 20, 2024 08:51
Copy link
Contributor

@arjenhuitema arjenhuitema left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@arjenhuitema arjenhuitema merged commit 1ef2893 into main Dec 20, 2024
2 checks passed
@arjenhuitema arjenhuitema deleted the users/jtracey93/feat/add-policy-faq branch December 20, 2024 08:55
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 this pull request may close these issues.

2 participants