updateAttribute fails with hostname(true) in minifi-cpp

[Tom Burton <to...@cyhesion.com>]

I have had minifi-cpp failing to go beyond an updateAttribute processor if I have a dynamic property being polulated with the FQDN using ${hostname(true)}.  It throws an error saying it is expecting a ")" or a ",".  It works fine when just using ${hostname()}.  This is running on an environment without a domain controller and the endpoint does not have an entry in the dns, so I would expect fqdn to provide the same result as a simple hostname.  When interrogating
# hostname -fqdn
it provides the same response as
# hostname
I'm running it on Centos7

Yours, Tom

Re: updateAttribute fails with hostname(true) in minifi-cpp

[Andy Christianson <ai...@protonmail.com>]

Tom,

The current hostname() implementation supports no arguments. Support for the FQDN argument will come with https://issues.apache.org/jira/browse/MINIFICPP-368.

The error message you're getting could certainly be improved. It could be that we have a bug with regard to subjectless functions with arguments. If that's the case, it will come to light when MINIFICPP-368 is completed (this ticket is on the near-term plan).

Regards,

Andy I.C.

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On March 29, 2018 3:37 AM, Tom Burton <to...@cyhesion.com> wrote:

> I have had minifi-cpp failing to go beyond an updateAttribute processor if I have a dynamic property being polulated with the FQDN using ${hostname(true)}.  It throws an error saying it is expecting a “)” or a “,”.  It works fine when just using ${hostname()}.  This is running on an environment without a domain controller and the endpoint does not have an entry in the dns, so I would expect fqdn to provide the same result as a simple hostname.  When interrogating
>
> # hostname –fqdn
>
> it provides the same response as
>
> # hostname
>
> I’m running it on Centos7
>
> Yours, Tom