[
https://issues.apache.org/jira/browse/KNOX-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683042#comment-17683042
]
Philip Zampino commented on KNOX-2871:
--------------------------------------
Discovery is already an option in descriptors. Omitting discovery details
should result in the generation of the associated topology if discovery is no
configured or cannot be performed.
I don't agree that there is a need for a "dummy" discovery type.
I can see that discovery-type defaults to a specific type if unspecified, but I
suspect this only happens if the discovery-address is specified. Therefore, I
think the "dummy" discovery type is accomplished by omitting all the
discovery-related attributes from the descriptor. If that is not the case, then
that is a bug IMO.
> Add "Skip" Service Discovery Type
> ---------------------------------
>
> Key: KNOX-2871
> URL: https://issues.apache.org/jira/browse/KNOX-2871
> Project: Apache Knox
> Issue Type: Task
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
>
> Currently if the discovery-type is set to null or an empty string then it
> will default to "ClouderaManager". If service discovery fails for any reason
> then the topology is not going to be generated. In some cases the user wants
> to use static service URLs for the services while also keeping discovery
> enabled. A dummy service discovery type that always returns an empty service
> list would make this possible.
> cc.: [~smolnar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
