curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nirdothan <>
Subject [GitHub] curator pull request: Support EPHEMERAL_SEQUENTIAL nodes for Servi...
Date Mon, 21 Mar 2016 10:24:32 GMT
Github user nirdothan commented on the pull request:
    - curator-x-discovery-server/README.txt
    `  Either "STATIC" or "PERMANENT". STATIC will get purged
                                                after the defined threshold has elapsed. PERMANENT
must be
                                                manually purged.`
    - curator-x-discovery-server/src/site/confluence/index.confluence
    `*Description:* {name} is the service name, {id} is the instance id. The request entity
is a _ServiceInstance_. This
    method registers a service instance. If the ServiceType is STATIC, the instance is registered
only for the pre\-defined period
    (defined in the DiscoveryContext). STATIC services must call putService at least once
per period. PERMANENT services are registered
    until they are manually deleted.`
    Only mention STATIC and PERMANENT, as those are the only allowed service types. DYNAMIC
isn't mentioned, so I guess there's no reason to mention DYNAMIC_SEQUENTIAL.
    The break and the validation check have been added

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message