awslabs / awslabs/aws-deployment-framework

[Bug]: adf-glabal-base-deployment stuck for missing permission in adf-bootstrap-update-deployment-role

Open
#755 0 comments 0 reactions 1 assignee Claimed by @sbkok View on GitHub
bug
Dominant language
Python
Stars
699
Forks
235
Avg merge
20h 53m
Merged PRs (30d)
7

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

When adf-glabal-base-deployment stack run it get stuck due to iam:PassRole missing permission.
Screenshot 2024-08-27 090946

### Expected Behavior

The adf-glabal-base-deployment cloudformation stack should run without error.

### Current Behavior

Any operation that will trigger the bootstrap pipeline which in turn ran the Cloudformation stack adf-global-base-deployment suffer from this behavior. i.e. changing account OU -

### Possible Solution

Probably we can consider adding the missing permission.

### ADF Version

4.0.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.