Large enterprises try to find a balance between controlling risk and empowering their developers in alignment with DevOps practices. Ideally developers are able to leverage AWS services and create optimized architectures for their applications. This solution addresses the risk and empowerment concerns by using AWS Service Catalog to exposed hardened AWS services to developers. By leveraging AWS Service Catalog products for each AWS Service; developers can create their own architectures with a self-service experience. This solution provides CloudFormation templates to make it easier for developers to automate the provisioning of the Service Catalog products.
  |
|||
| Main Code: 6,184 LOC (65 files) = YML (69%) + PY (30%) Secondary code: Test: 0 LOC (0); Generated: 0 LOC (0); Build & Deploy: 208 LOC (2); Other: 4,200 LOC (77); |
|||
| Duplication: 37% | |||
| File Size: 0% long (>1000 LOC), 62% short (<= 200 LOC) | |||
| Unit Size: 19% long (>100 LOC), 22% short (<= 10 LOC) | |||
| Conditional Complexity: 6% complex (McCabe index > 50), 59% simple (McCabe index <= 5) | |||
|
|
Logical Component Decomposition: primary (12 components) | ||
|
|
2 years, 9 months old
|
||
|
|
0% of code updated more than 50 times Also see temporal dependencies for files frequently changed in same commits. |
||
| Goals: Keep the system simple and easy to change (4) | |||
Latest commit date: 2021-10-28
|
0
commits
(30 days)
0
contributors
(30 days) |
|