[
https://issues.apache.org/jira/browse/CAMEL-26621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-26621:
-------------------------------------
Description:
Builds on the Floci AZ container that CAMEL-26615 adds to
{{camel-test-infra-azure-common}}.
The integration tests of camel-azure-functions ({{FunctionsProducerInvokeIT}},
{{FunctionsProducerManagementIT}}) need a real function app and subscription.
Floci AZ emulates function apps: its own admin API, the ARM
{{Microsoft.Web/sites}} resources, and HTTP invocation on
{{/api/<app>/<function>}}, served by a runtime container it starts through the
Docker socket (or by a stub answer in mocked mode).
h4. To investigate
The component invokes
{{https://<functionApp>.azurewebsites.net/api/<functionName>}} and manages
function apps through {{AppServiceManager}} against Azure Resource Manager.
Running it against Floci AZ needs a way to point both at another endpoint. The
outcome may be integration tests for the management operations only, a
component option for the endpoint (a change of its own), or the conclusion that
Floci AZ cannot cover this component yet.
Depends on CAMEL-26615.
_Claude Code on behalf of Andrea Cosentino_
was:
Part of the move of the Azure test-infra to Floci AZ (CAMEL-26613).
The integration tests of camel-azure-functions ({{FunctionsProducerInvokeIT}},
{{FunctionsProducerManagementIT}}) need a real function app and subscription.
Floci AZ emulates function apps: its own admin API, the ARM
{{Microsoft.Web/sites}} resources, and HTTP invocation on
{{/api/<app>/<function>}}, served by a runtime container it starts through the
Docker socket (or by a stub answer in mocked mode).
h4. To investigate
The component invokes
{{https://<functionApp>.azurewebsites.net/api/<functionName>}} and manages
function apps through {{AppServiceManager}} against Azure Resource Manager.
Running it against Floci AZ needs a way to point both at another endpoint. The
outcome may be integration tests for the management operations only, a
component option for the endpoint (a change of its own), or the conclusion that
Floci AZ cannot cover this component yet.
Depends on CAMEL-26613.
_Claude Code on behalf of Andrea Cosentino_
> camel-azure-functions - run the integration tests on Floci AZ
> -------------------------------------------------------------
>
> Key: CAMEL-26621
> URL: https://issues.apache.org/jira/browse/CAMEL-26621
> Project: Camel
> Issue Type: Test
> Components: camel-azure
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.24.0
>
>
> Builds on the Floci AZ container that CAMEL-26615 adds to
> {{camel-test-infra-azure-common}}.
> The integration tests of camel-azure-functions
> ({{FunctionsProducerInvokeIT}}, {{FunctionsProducerManagementIT}}) need a
> real function app and subscription.
> Floci AZ emulates function apps: its own admin API, the ARM
> {{Microsoft.Web/sites}} resources, and HTTP invocation on
> {{/api/<app>/<function>}}, served by a runtime container it starts through
> the Docker socket (or by a stub answer in mocked mode).
> h4. To investigate
> The component invokes
> {{https://<functionApp>.azurewebsites.net/api/<functionName>}} and manages
> function apps through {{AppServiceManager}} against Azure Resource Manager.
> Running it against Floci AZ needs a way to point both at another endpoint.
> The outcome may be integration tests for the management operations only, a
> component option for the endpoint (a change of its own), or the conclusion
> that Floci AZ cannot cover this component yet.
> Depends on CAMEL-26615.
> _Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
