Add dev command for running containers with docker-compose
Things to check
For any logging statements, is there any chance that they could be logging sensitive data?
Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.
Security considerations
There should be no direct security considerations to the code changes. But the effect of changes should be that customers can create CDNs with dedicated WAF ACLs, which allows better customization of WAF rules to their traffic patterns and more effective mitigation by Shield Advanced
Related to https://github.com/cloud-gov/private/issues/1098
Changes proposed in this pull request:
devcommand for running containers withdocker-composeThings to check
INFOand debugging statements are written withlog.debugor similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.Security considerations
There should be no direct security considerations to the code changes. But the effect of changes should be that customers can create CDNs with dedicated WAF ACLs, which allows better customization of WAF rules to their traffic patterns and more effective mitigation by Shield Advanced