The-DevOps-Daily/terraform-provider-validatefx

Add non_boolean_string validator

Open

#314 opened on Nov 10, 2025

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Go (25 forks)github user discovery
enhancementhacktoberfestterraform

Repository metrics

Stars
 (21 stars)
PR merge metrics
 (PR metrics pending)

Description

Implement a new provider::validatefx::non_boolean_string validator.

Description:

  • Validate that a string is not a boolean-like literal (true or false).

Acceptance criteria:

  1. Subtask: Implement non_boolean_string validator in internal/validators
  2. Subtask: Add unit tests for non_boolean_string validator
  3. Subtask: Add non_boolean_string function to internal/functions package
  4. Subtask: Add unit tests for non_boolean_string function
  5. Subtask: Register non_boolean_string in registry.go
  6. Subtask: Add documentation in examples/functions/non_boolean_string/function.tf
  7. Subtask: Update docs table using make docs command
  8. Subtask: Add integration test in integration/main.tf

Contributor guide

Research direction
Implement the non boolean string validator following the pattern of existing validators. Look at internal/validators, internal/functions, and registry.go for examples. Add unit tests and integration tests as specified in the subtasks.
Tech stack
goterraform
Domain
backenddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85