-
Notifications
You must be signed in to change notification settings - Fork 56
fix issue for aws iam profile [bsc#1169506] (1517) #1058
fix issue for aws iam profile [bsc#1169506] (1517) #1058
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Some suggestions to resolve.
Is there a test case for this fix? |
Good ask ;) @cclhsu please add a test case in |
I don't have an account with permission to create an IAM role to do the test, so personally, I'd prefer let QA testing this PR and approve it. |
0a0d178
to
d4e2eda
Compare
fix issue items for aws iam profile [bsc#1169506] Signed-off-by: cclhsu <clark.hsu@suse.com>
d4e2eda
to
9e754cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot test it because I do not have a non-openbare account. But it looks good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes worked for me as written.
Have tested after merged. Deployed successfully |
Have tested the deployment with and without iam_profile. It's working fine for me |
Fix issue items for aws iam profile [bsc#1169506]
Signed-off-by: cclhsu clark.hsu@suse.com
Why is this PR needed?
Fix issue items for aws iam profile [bsc#1169506]
Fixes #1517
What does this PR do?
Create aws_iam_role and aws_iam_policy
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:
Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
In terraform.tfvar, comment out following:
Deploy AWS in non-openbare account will not success.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Deploy AWS in non-openbare account will be successful.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises: