AWS cloudformation-cli documentation change
Summary
Updated product name references from 'AWS CloudFormation Command Line Interface (CLI) User Guide' to 'CloudFormation Command Line Interface (CLI) User Guide' and replaced 'AWS CloudFormation' with 'CloudFormation' in drift detection explanation.
Security assessment
Changes are branding/naming updates without technical security implications. No vulnerabilities or security features are mentioned.
Diff
diff --git a/cloudformation-cli/latest/userguide/resource-type-model-false-drift.md b/cloudformation-cli/latest/userguide/resource-type-model-false-drift.md index db782ea8e..8b1fdd74b 100644 --- a//cloudformation-cli/latest/userguide/resource-type-model-false-drift.md +++ b//cloudformation-cli/latest/userguide/resource-type-model-false-drift.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS CloudFormation](/cloudformation/index.html)[AWS CloudFormation Command Line Interface (CLI) User Guide](what-is-cloudformation-cli.html) +[Documentation](/index.html)[AWS CloudFormation](/cloudformation/index.html)[CloudFormation Command Line Interface (CLI) User Guide](what-is-cloudformation-cli.html) @@ -9 +9 @@ Defining a property transform for drift detection operations -When AWS CloudFormation performs drift detection on a resource, it looks up the value for each resource property as specified in the stack template, and compares that value with the current resource property value returned by the resource `read` handler. A resource is then considered to have drifted if one or more of its properties have been deleted, or had their value changed. In some cases, however, the resource may not be able to return the exact same value in the `read` handler as was specified in the stack template, even though the value is essentially the same and shouldn't be considered as drifted. +When CloudFormation performs drift detection on a resource, it looks up the value for each resource property as specified in the stack template, and compares that value with the current resource property value returned by the resource `read` handler. A resource is then considered to have drifted if one or more of its properties have been deleted, or had their value changed. In some cases, however, the resource may not be able to return the exact same value in the `read` handler as was specified in the stack template, even though the value is essentially the same and shouldn't be considered as drifted.