Files
terraform-provider-dokploy/.agents/skills/terraform-policy/examples/conversion/dms-endpoint-should-be-ssl-configured
Max Vojtkov a6d8aa8b52 A Terraform provider for Dokploy
Plugin-framework provider covering projects, environments, applications,
Compose stacks, managed databases, domains, mounts, ports, redirects,
basic auth, registries, SSH keys, certificates and backup destinations,
over Dokploy's tRPC-over-REST API.

The shim package exposes the provider to other Go modules, which is how
pulumi-dokploy bridges it.
2026-08-09 12:17:26 +03:00
..
2026-08-09 12:17:26 +03:00

DMS Endpoint Should Be SSL Configured

Source Sentinel Policy

dms-endpoint-should-be-ssl-configured.sentinel

Conversion Quality

Good

Why this converts reasonably well

The Sentinel version uses tfconfig/v2 to accept either a constant value or a reference for certificate_arn. tfpolicy cannot inspect Terraform config reference metadata the same way, but it can still validate that the planned certificate_arn value is non-empty.

Key translation notes

  • Config-oriented Sentinel checks become an end-state tfpolicy check on attrs.certificate_arn
  • tfpolicy focuses on the resulting planned value instead of whether it came from a literal or a reference

Limitations encountered

The tfpolicy version does not preserve the source-level distinction between constant values and references. It only checks that the final planned value is present.