Text Processingflags: g

Terraform Resource Block Header

Match the opening line of a Terraform `resource "type" "name" {` block, capturing the resource type and local name.

Try it in RegexPro →

Available in

JavaScript / ECMAScript

Browser-native RegExp. Default if you don't pick.

Python (re)

CPython stdlib `re`. Unicode-aware `\w` and `\d` by default.

Go (RE2)

Linear-time matching. No backreferences or lookarounds.

Pattern

regexengine-agnostic

resource\s+"([\w\-]+)"\s+"([\w\-]+)"\s*\{   (flags: g)

Raw source: resource\s+"([\w\-]+)"\s+"([\w\-]+)"\s*\{

How it works

resource\s+ matches the keyword and required whitespace. "([\w\-]+)" captures the resource type (e.g. `aws_instance`). "([\w\-]+)" captures the local name. The trailing `\s*\{` confirms a block opener (so we don't match string-literal `resource "x" "y"` in a comment).

Examples

Input

resource "aws_s3_bucket" "main" { bucket = "my-app" }

Matches

resource "aws_s3_bucket" "main" {

Input

resource "google_storage_bucket" "backups" {

Matches

resource "google_storage_bucket" "backups" {

Input

data "aws_caller_identity" "current" {}

No match

—

Common use cases

•Terraform module documentation generators
•Drift detection that catalogues resources
•Migration tooling between providers
•Cost-allocation reporting from .tf files

Related patterns

HCL / Terraform Variable Reference

Text Processing

Match Terraform / HCL references like `var.name`, `local.foo`, `module.x.output`, or `data.aws_ami.ubuntu.id`.

GraphQL Operation Header

Text Processing

Match GraphQL operation headers — `query`, `mutation`, or `subscription` — capturing the operation name.

C-Style Block Comment

Text Processing

Match C-style /* ... */ block comments across multiple lines.

JavaScript Variable Declaration

Text Processing

Match JavaScript / TypeScript variable declarations (`var`, `let`, `const`), capturing the keyword and identifier name.

←PreviousGitHub Actions Expression

NextHCL / Terraform Variable Reference→