[BUG] OpenSearch Reporting CLI Lambda always prepends "tmp" to email attachments

[aaronbrighton]

What is the bug?

When using the OpenSearch Reporting CLI Lambda function, the filename for email attachments always has "tmp" prepended to the filename.

How can one reproduce the bug?

Follow the instructions here (https://opensearch.org/docs/latest/dashboards/reporting-cli/rep-cli-lambda/).

What is the expected behavior?

Attachment filename should look something like this: opensearch-report-2023-03-31T12-00-51.433Z instead of tmpopensearch-report-2023-03-31T12-00-51.433Z.

What is your host/environment?

N/A

Do you have any screenshots?

See description for observed behavior.

Do you have any additional context?

It appears the following code which defines where to temporarily save the file is being propagated to the email function that attaches the file to the email and incorporating the folder name "tmp" in the value:

reporting-cli/src/run.js

Line 13 in 6feb950

options.filename = '/tmp/' + options.filename;

reporting-cli/src/email-helpers.js

Line 111 in 6feb950

filename: file,

Potentially easy fix by wrapping the value on line 111 above with path.basename()?

[joshuali925]

i feel this was a workaround for current directory not writable but user can write to /tmp dir? @rupal-bq

[rupal-bq]

i feel this was a workaround for current directory not writable but user can write to /tmp dir? @rupal-bq

Yes. In Lambda we can write only to the /tmp.

https://repost.aws/questions/QUoCCNNS59RryAKeEBezXFcg/how-to-work-around-directory-permissions-in-aws-lambda