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.
(aws-ecs): Provide an enableExecuteCommand method
See original GitHub issueWhen the enableExecuteCommand property was added, the enableExecuteCommand() method was made private. The logic that handles this property should have also been exposed as a method so that this feature could be enabled subsequent to construction of the construct.
Use Case
For use cases where we do not have direct access to construction of the construct, such as in the case of ApplicationLoadBalancedFargateService.
Proposed Solution
Move all logic related handling of the enableExecuteCommand configuration property into the enableExecuteCommand() method and make that method public.
- 👋 I may be able to implement this feature request
- ⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:9 (9 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
@ryparker Agree with your triage here. And thanks for providing a workaround!
@hoegertn these are side-effect causing methods, which have a legitimate purpose (imho), but I don’t see that for this method here