generated from camel.apache.org/kamelet
Update wiki Home page for drop-field-action
parent
b792b2dfe7
commit
96390d2bc8
36
Home.md
36
Home.md
@ -1,21 +1,29 @@
|
||||
# Deploy the Project on CamelX Platform
|
||||
# Drop Field Action
|
||||
|
||||
Deploy on CamelX Platform in three steps
|
||||
Removes a custom field by given name from the message in transit.
|
||||
|
||||
## Step 1: Create a release
|
||||
From the project space, click on **"Create a release"**
|
||||
The drop field action expects an application/json content type.
|
||||
|
||||
The new version is automatically available in the list
|
||||
If for example you have an object like '{ "foo":"John", "bar":30, "element":"hello" }' and your action has been configured with field as 'element', you'll get '{ "foo":"John", "bar":30 }' as a result because the field 'element' has been removed.
|
||||
|
||||
## Step 2: Deploy
|
||||
Click on **"Deploy"**
|
||||
## Metadata
|
||||
|
||||
- **Version:** Select the desired release
|
||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
||||
- **Configuration:** Select the configuration source
|
||||
- **Resources:** Set CPU and Memory
|
||||
| Property | Value |
|
||||
|----------|-------|
|
||||
| Type | action |
|
||||
| Group | Actions |
|
||||
| Namespace | Transformation |
|
||||
| Support Level | Stable |
|
||||
| Provider | Apache Software Foundation |
|
||||
|
||||
## Step 3: Expose
|
||||
Enable **"Expose"**
|
||||
## Properties
|
||||
|
||||
Choose an **API Gateway** (Internal, Public, etc.)
|
||||
| Name | Type | Required | Default | Description |
|
||||
|------|------|----------|---------|-------------|
|
||||
| `field` | string | ✓ | | The name of the field to be removed |
|
||||
|
||||
## Dependencies
|
||||
|
||||
- `camel:core`
|
||||
- `camel:jackson`
|
||||
- `camel:kamelet`
|
||||
|
||||
Loading…
Reference in New Issue
Block a user