Skip to content
This repository was archived by the owner on Jun 11, 2025. It is now read-only.

Fix/iam account member role bindings, and resource metrics#250

Merged
nxtcoder17 merged 2 commits into
release-v1.0.1from
fix/iam-account-member
Feb 6, 2024
Merged

Fix/iam account member role bindings, and resource metrics#250
nxtcoder17 merged 2 commits into
release-v1.0.1from
fix/iam-account-member

Conversation

@nxtcoder17
Copy link
Copy Markdown
Member

@nxtcoder17 nxtcoder17 commented Feb 6, 2024

Description

closes #248
closes #249

- There are no RoleBindings with `account-member` role, so, in case of
  resources eligible for users with `account-member` role, it used to
  end up in UnAuthorized. This commit fixes it.
@nxtcoder17 nxtcoder17 merged commit 90a112c into release-v1.0.1 Feb 6, 2024
@nxtcoder17 nxtcoder17 deleted the fix/iam-account-member branch February 6, 2024 11:06
Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

PR Type: Enhancement

PR Summary: This pull request introduces several enhancements and fixes across the IAM and observability functionalities. It addresses issues related to account member role bindings and resource metrics, improving the system's ability to handle user permissions and metrics retrieval more effectively. The changes include updates to error handling, the introduction of new GraphQL queries, and modifications to the way metrics are queried and displayed. Additionally, it refines the validation logic for role bindings and enhances the parsing of resource references.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.
  • Sourcery currently only approves 'Typo fix' PRs.
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
✅ Small diff: the diff is small enough to approve with confidence.
No details provided.

General suggestions:

  • Ensure that all new functionalities introduced are accompanied by adequate unit tests to maintain code quality and prevent regressions.
  • Consider reviewing the performance implications of the changes, especially those involving loops and data structure manipulations, to ensure that they do not introduce performance bottlenecks.
  • Review the debug logging statements to ensure that they do not inadvertently expose sensitive information.
  • It might be beneficial to document the rationale behind significant changes or new functionalities for future reference and clarity.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 Unable to get resource metrics 🐛 IAM Unauthorized while reading logs or metrics

1 participant