cdk.context.json best practice #15
Description
Could you clarify the best practice here regarding cdk.context.json and CI/CD? Should it be committed to source control? When deploying multiple environments to a single account via CI/CD, how does cdk.context.json get generated for, say, prod environment and committed to source control when synth may only be happening for prod via CI/CD server?