Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
(pipelines): A guidance to writing programatic smoke test
See original GitHub issueGeneral Issue
How to get a proper permission (assume role) to launch integration test
The Question
In short, I am looking on a problem of defining a test after a stage deployment that utilized said stage outputs and runs integration/smoke tests using Python’s pytest + boto3. Now I am using ShellStep as post stage step and envFromCfnOutputs feature to get ahold of couple of ARNs and more importantly a role’s ARN that allows to access deployed resources.
Question is: how I assume said role? Obviously the role created by CDK backing ShellStep’s CodeBuild is not accessible to me. What can I do?
CDK CLI Version
1.139.0
Framework Version
No response
Node.js Version
No response
OS
No response
Language
Python
Language Version
3.10.1
Other information
Looking for guidance 😉
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
yes
To control the role used in a ShellStep, you should switch to
CodeBuildStep. It exposesroleand you can add statements to the policy directly.