AWS cloudformation-cli documentation change
Summary
Updated documentation to replace 'AWS CloudFormation' with 'CloudFormation' in titles, content, and links. No functional changes to Hook modeling process.
Security assessment
Changes are purely branding/naming convention updates (removing 'AWS' prefix). No security-related content modifications, vulnerability fixes, or new security features documented.
Diff
diff --git a/cloudformation-cli/latest/hooks-userguide/hooks-model.md b/cloudformation-cli/latest/hooks-userguide/hooks-model.md index 68dbcface..2bd13fe36 100644 --- a//cloudformation-cli/latest/hooks-userguide/hooks-model.md +++ b//cloudformation-cli/latest/hooks-userguide/hooks-model.md @@ -5 +5 @@ -# Modeling custom AWS CloudFormation Hooks +# Modeling custom CloudFormation Hooks @@ -7 +7 @@ -Modeling custom AWS CloudFormation Hooks involves creating a schema that defines the Hook, its properties, and their attributes. When you create your custom Hook project using the `cfn init` command, an example Hook schema is created as a JSON-formatted text file, ``hook-name`.json`. +Modeling custom CloudFormation Hooks involves creating a schema that defines the Hook, its properties, and their attributes. When you create your custom Hook project using the `cfn init` command, an example Hook schema is created as a JSON-formatted text file, ``hook-name`.json`. @@ -9 +9 @@ Modeling custom AWS CloudFormation Hooks involves creating a schema that defines -Target invocation points and target actions specify the exact point where the Hook is invoked. _Hook handlers_ host executable custom logic for these points. For example, a target action of the `CREATE` operation uses a `preCreate` handler. Your code written in the handler will invoke when Hook targets and services perform a matching action. _Hook targets_ are the destination where hooks are invoked. You can specify targets such as, AWS CloudFormation public resources, private resources, or custom resources. Hooks support an unlimited number of Hook targets. +Target invocation points and target actions specify the exact point where the Hook is invoked. _Hook handlers_ host executable custom logic for these points. For example, a target action of the `CREATE` operation uses a `preCreate` handler. Your code written in the handler will invoke when Hook targets and services perform a matching action. _Hook targets_ are the destination where hooks are invoked. You can specify targets such as, CloudFormation public resources, private resources, or custom resources. Hooks support an unlimited number of Hook targets. @@ -81 +81 @@ You can use the following schema file as a starting point to define your Hook. U - * [Modeling custom AWS CloudFormation Hooks using Java](./hooks-model-java.html) + * [Modeling custom CloudFormation Hooks using Java](./hooks-model-java.html) @@ -83 +83 @@ You can use the following schema file as a starting point to define your Hook. U - * [Modeling custom AWS CloudFormation Hooks using Python](./hooks-model-python.html) + * [Modeling custom CloudFormation Hooks using Python](./hooks-model-python.html)