feat: updated coming-from-mongock to add new MongockSupport annotation fields (#116)

Author: osantana85

docs/resources/coming-from-mongock.md

@@ -4,6 +4,7 @@ sidebar_position: 999
 ---
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
+import VersionBadge from '@site/src/components/VersionBadge';
 
 # Coming from Mongock
 
@@ -105,6 +106,38 @@ A full explanation of why this is required (and how Mongock’s model differs fr
 
 **That’s all you need to activate Mongock support.** From there, Flamingock handles the detection of legacy changes, audit import, and stage ordering automatically.
 
+### Optional configuration <VersionBadge version="1.1.0" />
+
+The `@MongockSupport` annotation includes optional fields you can use to configure how Flamingock reads Mongock’s audit log. Both fields accept **literal values** or **property placeholders**.
+
+| Name | Type | Default | Description |
+| --- | --- | --- | --- |
+| `origin` | `String` | "" | The Mongock audit origin to read from. Supports literal values and placeholders. When empty (default), Flamingock uses Mongock’s default origin value. |
+| `emptyOriginAllowed` | `String` | "" | Whether Flamingock should allow an empty origin during import. Supports literal values and placeholders. Allowed values are `true`, `false`, or empty. When empty (default), it is treated as `false`, and Flamingock will fail if the origin is empty. |
+
+:::info
+`origin` value by Mongock driver:
+
+- **MongoDB**: collection name.
+- **DynamoDB**: table name.
+- **Couchbase**: either the collection name (implicit `_default` scope) or `{scope}.{collection}` (for example, `"myscope.mycollection"`).
+:::
+
+Example:
+
+```java
+@MongockSupport(
+    targetSystem = "mongodb-target-system",
+    origin = "customChangeLog",
+    emptyOriginAllowed = "true"
+)
+public class Application { }
+```
+
+:::tip Property placeholders
+Configuration values can be set by referencing properties in the Flamingock context using the format `${my.custom.property:defaultValue}`.
+:::
+
 ## Understanding the target system for Mongock migrations
 
 Mongock and Flamingock follow different models when interacting with external systems, so it is important to understand how the `targetSystem` defined in `@MongockSupport` fits into a Flamingock application.