[jira] [Created] (KNOX-1017) Add support for enabling "Strict-Transport-Security" header in knox reponses

Latha Appanna created KNOX-1017: Summary: Add support for enabling "Strict-Transport-Security" header in knox reponses Key: KNOX-1017 URL: https://issues.apache.org/jira/browse/KNOX-1017 Project:

[jira] [Updated] (KNOX-1013) Monitor Ambari for Topology changes

[ https://issues.apache.org/jira/browse/KNOX-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1013: --- Description: Knox should provide the option to monitor an Ambari cluster for which it has deployed a

[jira] [Created] (KNOX-1015) ZooKeeper-Based Service Discovery

Phil Zampino created KNOX-1015: -- Summary: ZooKeeper-Based Service Discovery Key: KNOX-1015 URL: https://issues.apache.org/jira/browse/KNOX-1015 Project: Apache Knox Issue Type: Sub-task

[jira] [Created] (KNOX-1014) Service Discovery and Topology Generation Framework

Phil Zampino created KNOX-1014: -- Summary: Service Discovery and Topology Generation Framework Key: KNOX-1014 URL: https://issues.apache.org/jira/browse/KNOX-1014 Project: Apache Knox Issue

[jira] [Created] (KNOX-1012) ZooKeeper Monitor for Knox Topology Config Changes

Phil Zampino created KNOX-1012: -- Summary: ZooKeeper Monitor for Knox Topology Config Changes Key: KNOX-1012 URL: https://issues.apache.org/jira/browse/KNOX-1012 Project: Apache Knox Issue Type:

[jira] [Updated] (KNOX-970) Add support for proxying NiFi

[ https://issues.apache.org/jira/browse/KNOX-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated KNOX-970: - Attachment: KNOX-970-PR-9.patch > Add support for proxying NiFi > - > >

[jira] [Created] (KNOX-1010) Remote Discovery of Knox Topology Configuration

Phil Zampino created KNOX-1010: -- Summary: Remote Discovery of Knox Topology Configuration Key: KNOX-1010 URL: https://issues.apache.org/jira/browse/KNOX-1010 Project: Apache Knox Issue Type:

[jira] [Updated] (KNOX-1009) Support Externalized Provider Configuration References From topology descriptors

[ https://issues.apache.org/jira/browse/KNOX-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1009: --- Labels: kip-8 (was: ) > Support Externalized Provider Configuration References From topology >

Re: KIP-8 Service Discovery and Topology Generation

I agree that named provider config should suffice. HA and AclsAuth reference services within the topology and therfore will present a challenge for reuse across topologies. We'll need to figure that out. On Aug 31, 2017 9:12 AM, "Philip Zampino" wrote: > Concerning the

Re: KIP-8 Service Discovery and Topology Generation

Concerning the externalized provider configuration, the idea is to have sets of "named" (unique ID'd) config, which can be referenced by any Knox topology. So, you could have a single provider configuration that is applied (by reference) to all your cluster topologies, if that made sense for your

[jira] [Commented] (KNOX-738) Remove references to deprecated httpclient class DefaultHttpClient

[ https://issues.apache.org/jira/browse/KNOX-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148727#comment-16148727 ] ASF subversion and git services commented on KNOX-738: -- Commit

[jira] [Updated] (KNOX-738) Remove references to deprecated httpclient class DefaultHttpClient

[ https://issues.apache.org/jira/browse/KNOX-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated KNOX-738: - Fix Version/s: 0.14.0 > Remove references to deprecated httpclient class DefaultHttpClient

Re: KIP-8 Service Discovery and Topology Generation

> > As a result, I'm wondering if Knox should support provider configuration > references in topology.xml, rather than having to duplicate it across > descriptors. +1 to Phil's remark above. Adding to that as Knox provides multi-cluster support, can we have external provider config cluster-wise?