CloudTruth Documentation
Sign InAPIIntegrationsGitHubVisit our website
  • Overview
  • Getting Started
  • Architecture
    • 🔒Security Overview
  • Copilot
  • 🏢Org management
    • Account Setup
    • Access Control
      • 🔑API Tokens
      • 🌐Protecting Projects and Environments
      • 👥Users
    • Audit Log
  • 🛠️Config Management
    • Projects
    • Parameters
      • Sharing Config Data
      • Parameter Management
        • Internal Values
          • Dynamic Values
        • External Values
          • Terraform Remote State Files
        • Parameter Override
        • Environment Value Override
      • Parameter and Parameter Value Inheritance
      • Value Comparison
      • Value History
      • Value Validation
      • Value Expiration
    • Environments and Tags
    • Templates
      • 📒Sample Templates
    • Actions
      • Import Actions
      • Push Actions
    • CLI & API
      • CloudTruth CLI
      • Rest API
    • Integrations
      • Argo CD
      • Atlassian Compass
      • AWS
        • AWS Connection
        • AWS Role
          • CloudFormation
          • Terrraform
          • AWS Console
        • Parameter Store (SSM)
        • S3
        • Secrets Manager
      • Azure Key Vault
      • Bitbucket Pipelines
      • Docker
      • Docker Compose
      • GitHub
      • GitHub Actions
      • GitLab
      • Harness
      • Jenkins
      • Kubernetes
      • Pulumi
      • Terraform
      • Terragrunt
      • Explorer
      • Circle CI
    • Events, Notifications, Webhooks
    • Types
  • 🔎REPORTING
    • Compare
    • History
    • Expirations
  • 🚀PRODUCT
    • What is CloudTruth?
    • Interactive Demo
    • Kubernetes
    • Terraform
    • CI/CD Pipeline Configuration
    • Cloud CMDB
    • Secrets Management
    • GitOps
    • Our Manifesto
    • Open Source
    • FAQs
    • Our Mission
  • 📚Reference
    • 🎓Quick Start Videos
      • What is CloudTruth?
      • CloudTruth in Action
      • Environments and Projects
      • Secrets, Parameters, ENV variables
      • Audit Logs, RBAC, SSO
      • Containers - Kubernetes, Docker
      • Infrastructure as Code (IaC) - Terraform, Cloudformation, CDK, Azure Bicep, Pulumi
      • CICD Pipelines - GitHub Actions, ArgoCD, Jenkins, CircleCI, Harness, GitLab Pipelines
      • AWS Videos - Secret Manager, Parameter Store, S3, IAM
      • Azure Videos - Azure DevOps, Azure Bicep, PowerShell
    • Knowledge Base
      • Best Practices
        • Versioned Releases
      • CLI
        • History comparison of deleted parameters with null values
      • Integrations
        • Advanced AWS IAM policy permissions
        • K8s pull image from private Docker registry
        • S3 Region Selection
      • Templates
        • Templates render quotations in key values as quot
    • Roadmap and New Features
    • JMESPath Reference
    • REST API
Powered by GitBook

Copyright© 2023 CloudTruth

On this page

Was this helpful?

  1. Config Management
  2. Parameters

Value Validation

This, not that.

PreviousValue HistoryNextValue Expiration

Last updated 1 year ago

Was this helpful?

Nobody enjoys typos, especially ones that make their way into production and cause outages. With CloudTruth you can set a series of rules and typing on your parameters to ensure they meet a specific criteria, or syntax, that meet specific intended values.

Creating Parameter Rules

Rules are set on the parameter itself within a selected project that provide validation of values across all of the parameters environments.

The following are the current rules you can set on your parameters.

Parameter Type
Allowed Rules

String

Minimum Length

Maximum Length

Regular Expression

Integer

Minimum

Maximum

Bool

Boolean Types

We provide a regular expression rule for strings to come up with whatever crafty regex you require.

The Type and Rules can be set during parameter creation or when editing a parameter.

When adding rules to an existing parameter, CloudTruth will check across all environments to make sure the existing values conform to the new rule(s). If any of the values do NOT conform to the proposed rule change, the app will display the what and how the rule conflicts. Those conflicts will have to be remediated prior to setting the rule.

The rule type and constraint settings are listed in the parameter's detail page for convenience.

🛠️
Value typed is shorter than the minimum length
Value is longer than maximum allowed length
Adding a rule to an existing parameter where an environment value does not match the rule
Error message when rule cannot be applied due to an existing value mismatch