feat: add separate task definition

[budde377]

Description

Extract task definitions into their own submodule (just like container definitions) and allow creating task definitions directly on the cluster.

Motivation and Context

We are looking to run scheduled tasks through AWS EventBridge following this approach. This change will allow us to define a task independently of a service reusing all the heavy lifting of this module wrt. e.g. iam policies.

Breaking Changes

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[bryantbiggs]

we already support this today

terraform-aws-ecs/examples/fargate/main.tf

Lines 215 to 264 in 17b8a18

	################################################################################
	# Standalone Task Definition (w/o Service)
	################################################################################
	module "ecs_task_definition" {
	source = "../../modules/service"
	# Service
	name = "${local.name}-standalone"
	cluster_arn = module.ecs_cluster.arn
	create_service = false
	# Task Definition
	volume = {
	ex-vol = {}
	}
	runtime_platform = {
	cpu_architecture = "ARM64"
	operating_system_family = "LINUX"
	}
	# Container definition(s)
	container_definitions = {
	al2023 = {
	image = "public.ecr.aws/amazonlinux/amazonlinux:2023-minimal"
	mountPoints = [
	{
	sourceVolume = "ex-vol",
	containerPath = "/var/www/ex-vol"
	}
	]
	command = ["echo hello world"]
	entrypoint = ["/usr/bin/sh", "-c"]
	}
	}
	subnet_ids = module.vpc.private_subnets
	security_group_egress_rules = {
	all = {
	ip_protocol = "-1"
	cidr_ipv4 = "0.0.0.0/0"
	}
	}
	tags = local.tags
	}

[budde377]

Excelent, thanks!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.