Does this query look like an instance-type pattern (glob or regex) rather
than a natural-language phrase? True when it contains a glob wildcard (*/?)
or a regex metacharacter (see looksLikeRegex).
DELIBERATE DIVERGENCE from the Go tool: Go also routes a bare single word
matching ^[a-z]+\d (e.g. "a100", "c6i", "m7i.large") to the pattern path.
That collides with GPU model names — Go's find a100 searches instance-type
names for ^a100$ and finds nothing, since no instance is literally named
"a100". truffle-ts instead sends bare words through the natural-language
parser, which resolves "a100" → the A100 instance types and "graviton" → its
families. To force a name pattern, use an explicit glob: a100*, m7i*,
c6i.*. (This is why parse still guards the no-constraint case, so a stray
unknown bare word can't fall through to a match-everything ".*".)
Does this query look like an instance-type pattern (glob or regex) rather than a natural-language phrase? True when it contains a glob wildcard (
*/?) or a regex metacharacter (see looksLikeRegex).DELIBERATE DIVERGENCE from the Go tool: Go also routes a bare single word matching
^[a-z]+\d(e.g. "a100", "c6i", "m7i.large") to the pattern path. That collides with GPU model names — Go'sfind a100searches instance-type names for^a100$and finds nothing, since no instance is literally named "a100". truffle-ts instead sends bare words through the natural-language parser, which resolves "a100" → the A100 instance types and "graviton" → its families. To force a name pattern, use an explicit glob:a100*,m7i*,c6i.*. (This is why parse still guards the no-constraint case, so a stray unknown bare word can't fall through to a match-everything ".*".)