Let your CI/CD workflow flexibly handle any repository folder structure so you can instead focus on writing the actual code!
I was working on setting the CI/CD workflow of a large repository involving different infrastructure components, encapsulated in folders, the other day. Many questions had to be asked: do we need to separate repositories for different “blocks” having different deployment workflows? how should we organize directories within the same repository? how do we handle deployment dependencies — e.g., when one component (folder) needs to be deployed exactly before or after the other.
In order to remove the need for all…
The mappings section of a cloudformation template allows specific values to be mapped into keys to be used at different parts of your template. This might not seem all too important but as soon as the template of your stack gets longer with more resources, and as your stack references other stack resources, then this becomes a deciding factor in your final template’s readability and adaptability to changes.
・Software Engineer — AWS, NodeJS, Python, Angular, Docker