As a CSE engineer, I want to re-use terraform templates for Azure resources across projects to avoid redevelopment of already existing assets.

[xtophs]

Tagging @timfpark

[charleszipp]

@rickrain @xtophs

This is the directory structure i would suggest if you plan to share/merge cobalt and bedrock. I tried to document this very quickly before having to go on leave. Im sure theres plenty of valid changes in terms of the organization of the components. However, i think the pattern is consistent with bedrock's approach to modules. It does however, incorporate some of the more abstract and convention based approaches we are using in cobalt. I feel the final result would include the best of both worlds.

- ./components <<PIPELINE SHOULD NEVER RUN THESE INDIVIDUALLY>>
	- ./network
		- main.tf
			- vnet
	- ./keys
		- main.tf
			- key vault
	- ./ingress
		- ./multi-region
			- main.tf
				- traffic manager
		- ./single-region
			- main.tf
				- app gateway
	- ./monitoring
		- main.tf
			- azure monitor
	- ./compute
		- ./bedrock
		- ./cobalt

- ./solutions <<PIPELINE SHOULD RUN ONE OF THESE>>
	- ./single-region-bedrock
		- main.tf
			- .../../components/network (reuses network module)
			- .../../components/keys
			- .../../components/ingress/single-region
			- ../../components/bedrock
	- ./multi-region-bedrock
		- main.tf
			- .../../components/network
			- .../../components/keys
			- .../../components/ingress/multi-region
			- ../../components/bedrock
	- ./single-region-cobalt
		- main.tf
			- .../../components/network (reuses network module)
			- .../../components/keys
			- .../../components/ingress/single-region
			- ../../components/cobalt
	- ./multi-region-cobalt
		- main.tf
			- .../../components/network
			- .../../components/keys
			- .../../components/ingress/multi-region
			- ../../components/cobalt

[rickrain]

This should really be an epic.