[
https://issues.apache.org/jira/browse/CAMEL-18992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746325#comment-17746325
]
Claus Ibsen edited comment on CAMEL-18992 at 7/24/23 10:19 AM:
---------------------------------------------------------------
AWS components with health-checks
- ec2 (producer) disabled in code
- s3 (consumer) *DONE*
- aws2-athena (producer) disabled in code
- aws-cloudtrail (consumer) *DONE*
- aws2-cw (producer) disabled in code
- aws2-ddb (producer) disabled in code
- aws2-ddbstream (consumer) *DONE*
- aws2-ecs (producer) disabled in code
- aws2-eks (producer) disabled in code
- aws2-eventbridge (producer) disabled in code
- aws2-iam (producer) disabled in code
- aws2-kinesis (consumer) *DONE*
- aws2-kinesis (producer) no health check
- aws2-lambda (producer) disabled in code
- aws2-mq (producer) disabled in code
- aws-secrets-manager (producer) *DONE*
was (Author: davsclaus):
AWS components with health-checks
- ec2 (producer) disabled in code
- s3 (consumer) *DONE*
- aws2-athena (producer) disabled in code
- aws-cloudtrail (consumer) *DONE*
- aws2-cw (producer) disabled in code
- aws2-ddb (producer) disabled in code
- aws2-ddbstream (consumer) *DONE*
- aws2-ecs (producer) disabled in code
> Health Check: Provide a way to disable health check on specific
> component/producer/consumers
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-18992
> URL: https://issues.apache.org/jira/browse/CAMEL-18992
> Project: Camel
> Issue Type: Improvement
> Reporter: Andrea Cosentino
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.0.0
>
>
> As of today we are able to exclude from health check some consumers in this
> way
> camel.health.exclude-pattern = consumer:aws-s3-*
> But it would be nice to be able to do something like
> camel.component.aws-s3.health.disabled = true
> camel.component.aws-s3.health.consumers.disabled = true
> camel.component.aws-s3.health.producer.disabled = false
> I'm adding 4.0, 3.21.0 and 3.20.2 as fix version, since 3.20 will be an LTS
> for a long time and this would be a useful feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
