feat(engines): add suga properties for platform properties.

[tjholm]

A proposal for exposing additional suga properties to the platform editor.

e.g. "name": "${suga.stack_id}-vpc" using the stack id for unique naming

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR extends the Terraform deployment engine with a new "suga" token source. It introduces a sugaProperties map field to the TerraformDeployment struct initialized with a stack_id entry, adds token resolution logic for the "suga" prefix in the resolve handler, and updates the token regex patterns to recognize tokens starting with "suga" alongside existing prefixes (infra, var, self).

Possibly related PRs

• fix(engines): resolve format variables and multi variables #87: Directly extends token handling with a new "suga" source and sugaProperties initialization
• fix(engines): reduce valid token chars #114: Modifies token recognition regexes in engines/terraform/token.go
• fix(engines): update token parsing to use prefixes #110: Updates token parsing and resolution logic for prefixed tokens

Suggested reviewers

• jyecusch
• davemooreuws
• raksiv

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "add suga properties for platform properties" accurately describes the core changes: introducing a new suga token source and associated properties field to TerraformDeployment. The title directly aligns with the main objective of exposing suga properties to the platform editor, and a developer reviewing history would clearly understand the purpose of this changeset without ambiguity.
Description Check	✅ Passed	The description is directly relevant to the changeset, explaining that it exposes suga properties for the platform editor and providing a concrete usage example (${suga.stack_id}-vpc). This example corresponds to the implemented functionality where stack_id is initialized in sugaProperties, demonstrating the author understands and articulates the changes appropriately.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

engines/terraform/resolve.go (1)

127-145: Clean implementation of suga property resolution.

The implementation correctly validates path components, provides helpful error messages listing available properties, and explicitly disallows nested access. The pattern is consistent with other token sources.

Consider adding a brief comment above the case explaining what suga properties are and their intended use (e.g., "platform-provided properties like stack_id for resource naming"). This would help future maintainers understand the purpose.

+	// suga properties are platform-provided values (e.g., stack_id) used for resource naming and configuration
 	case "suga":
 		if len(specRef.Path) < 1 {

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bff2b5c and 522f2d1.

📒 Files selected for processing (3)

• engines/terraform/deployment.go (2 hunks)
• engines/terraform/resolve.go (1 hunks)
• engines/terraform/token.go (1 hunks)

🔇 Additional comments (2)

engines/terraform/token.go (1)

48-49: LGTM - regex patterns updated correctly.

Both patterns consistently include "suga" in the alternation group, enabling token recognition for suga.* references.

engines/terraform/deployment.go (1)

31-31: Good foundation for suga properties.

The field and initialization are implemented correctly. The map is properly initialized in the constructor with stack_id, preventing nil access issues. The use of stackId.Result() provides a token reference that will resolve during Terraform synthesis.

Also applies to: 64-66