[
https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-17012:
-----------------------------------
Description:
The listAliases operation unduly fails in aws lambda.
The underlying request is not built in the Lambda2Producer class and the
functionVersion parameter is unduly required.
>From the doc
>[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the
>functionVersion should not be required. From the history I've been able to
>grab, it seems it was never required in which case I guess it should be fine
>to relax the constraint.
A workaround is to use pojoRequest and define the request explicitly by hand.
was:
The listAliases operation unduly fails in aws lambda.
The underlying request is not built and the functionVersion parameter is unduly
required.
>From the doc
>[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the
>functionVersion should not be required. From the history I've been able to
>grab, it seems it was never required in which case I guess it should be fine
>to relax the constraint.
A workaround is to use pojoRequest and define the request explicitly by hand.
> camel-aws2-lambda: ListAliases unduly return "Function Version must be
> specified to list aliases for a function"
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-17012
> URL: https://issues.apache.org/jira/browse/CAMEL-17012
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
> Affects Versions: 3.12.0
> Reporter: Alex Dettinger
> Priority: Minor
> Fix For: 3.11.3, 3.13..
>
>
> The listAliases operation unduly fails in aws lambda.
> The underlying request is not built in the Lambda2Producer class and the
> functionVersion parameter is unduly required.
> From the doc
> [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the
> functionVersion should not be required. From the history I've been able to
> grab, it seems it was never required in which case I guess it should be fine
> to relax the constraint.
>
> A workaround is to use pojoRequest and define the request explicitly by hand.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
