Atru/create meta args reference topics

[trujillo-adam]

This PR reverses the strategy applied in PR-530 and aggregates meta-arguments into their own reference section with separate pages for each argument.

[github-actions]

Vercel Previews Deployed

Name	Status	Preview	Updated (UTC)
Dev Portal	🔄 Building (Inspect)	---	---
Unified Docs API	✅ Ready (Inspect)	Visit Preview	Thu Oct 30 03:14:38 UTC 2025

[github-actions]

Broken Link Checker

No broken links found! 🎉

[judithpatudith]

I don't think this is accurate because Terraform uses depends on during lots of operations, not just creation. Is there a reason not to use the original language here?

[judithpatudith]

Should we use this example if it's not a real use case? Let's find a real one instead

[BrianMMcClain]

Yeah I don't believe there's ever a case this would happen, at least off of the top of my head.

What about a scenario where configuration requires an RDS instance to be launched first before the user spins up an EC2 instance that connects to it? It's not a relationship you have to explicitly declare 100% of the time (if you pass the DB IP through the EC2 resource user_data string, for example), but there's plenty of times a user could run into this.

Full config example, feel free to chop down if you go this route

provider "aws" {
  region = "us-east-2"
}

data "aws_ami" "ubuntu" {
  most_recent = true

  filter {
    name   = "name"
    values = ["ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-*"]
  }

  filter {
    name   = "virtualization-type"
    values = ["hvm"]
  }

  owners = ["099720109477"] # Canonical
}

resource "aws_db_instance" "api" {
  allocated_storage   = 10
  db_name             = "api_db"
  engine              = "postgres"
  engine_version      = "17.4"
  instance_class      = "db.t3.micro"
  username            = "foo"
  password            = "foobarbaz"
  skip_final_snapshot = true
}

resource "aws_instance" "api" {
  ami           = data.aws_ami.ubuntu.id
  instance_type = "t3.micro"

  depends_on = [aws_db_instance.api]
}

[BrianMMcClain]

What do you think about putting this above the Usage section, since we use the count.index value in the example above? Not sure if that breaks our content type too much, though.

[BrianMMcClain]

I think the exact wording here depends if we decide to move the "count objects" H2 above this or not, but we should call out what ${count.index} is doing in this context

[BrianMMcClain]

Yeah I don't believe there's ever a case this would happen, at least off of the top of my head.

What about a scenario where configuration requires an RDS instance to be launched first before the user spins up an EC2 instance that connects to it? It's not a relationship you have to explicitly declare 100% of the time (if you pass the DB IP through the EC2 resource user_data string, for example), but there's plenty of times a user could run into this.

Full config example, feel free to chop down if you go this route

provider "aws" {
  region = "us-east-2"
}

data "aws_ami" "ubuntu" {
  most_recent = true

  filter {
    name   = "name"
    values = ["ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-*"]
  }

  filter {
    name   = "virtualization-type"
    values = ["hvm"]
  }

  owners = ["099720109477"] # Canonical
}

resource "aws_db_instance" "api" {
  allocated_storage   = 10
  db_name             = "api_db"
  engine              = "postgres"
  engine_version      = "17.4"
  instance_class      = "db.t3.micro"
  username            = "foo"
  password            = "foobarbaz"
  skip_final_snapshot = true
}

resource "aws_instance" "api" {
  ami           = data.aws_ami.ubuntu.id
  instance_type = "t3.micro"

  depends_on = [aws_db_instance.api]
}

[judithpatudith]

I didn't make it all the way through the blocks pages, but I looked at all the meta-argument pages and they look really good! Thank you for these!

[judithpatudith]

I think we only want this note in the 1.14 docs and onward?

[trujillo-adam]

The other way around. We added it as a temporary way to make the beta features more discoverable. We'll take it out when 1.14 becomes the latest.

[judithpatudith]

Should this come before provider and providers to match the order of the reference pages?

[judithpatudith]

Many of the other H3s have examples but pre and post conditions don't. I do see there are examples in the examples section, so this isn't a blocker, just inconsistent.