feat: add RDS/Lambda/EBS/S3 permissions for infrastructure explorer - #208
n3ziniuka5 wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
cf52a7e to
e9877b8
Compare
e9877b8 to
b81ead0
Compare
b81ead0 to
db24c5e
Compare
db24c5e to
d48d4d8
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Description
Allows the AWS resource catalog integration to pull metadata from RDS instances, Lambda functions, EBS columes, and S3 buckets
Fixes:How Has This Been Tested?
Deployed the stack to research account and then ran
cloud-collectorlocally to verify that the new permissions are enough for the infra explorer.Checklist: