martinzink commented on a change in pull request #1268:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1268#discussion_r823870200
##########
File path: PROCESSORS.md
##########
@@ -1448,6 +1449,60 @@ In the list below, the names of required properties
appear in bold. Any other pr
|success|Files that have been successfully written to Azure storage are
transferred to this relationship|
+## PutGcsObject
+
+### Description
+
+Puts content into a Google Cloud Storage bucket
+### Properties
+
+In the list below, the names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates any
default values, and whether a property supports the NiFi Expression Language.
+
+| Name | Default Value | Allowable Values
| Description
|
+|---------------------------------------|---------------|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Bucket Name** | |
| The name of the Bucket to upload to. If left empty the _gcs.bucket_
attribute will be used by default.<br>**Supports Expression Language: true**
|
+| **Object Name** | |
| The name of the object to be uploaded. If left empty the _filename_
attribute will be used by default.<br>**Supports Expression Language: true**
|
Review comment:
afaik we cant extract the flowfile attributes via expression language
like Nifi can so we cant really use the same interface
Or are you referring to use **Key** instead of **Object Name**?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
