Streams assumes all applinks are stream providers

Description

Streams shouldn't assume all app links are streams providers, as the point of app links is to allow the host application to link to any application anywhere. While the primary use case has been Atlassian applications, this is definitely not the only type of link.

This bug is particularly affecting Remote Apps as it is causing OnDemand to hammer remote apps, which can be an expensive operation on certain PaaS providers. At a minimum, Streams should look for a streams.disable property on the applink to know not to hammer it.

Environment

None

Testing Notes

None

Activity

Show:
Eric Dalgliesh (public name)
June 7, 2013, 5:43 AM

I cloned here because it seems to not actually be fixed. By default streams should not treat applinks as providers. Applinks should have to opt in. Applinks to Atlassian products should probably do this by default.

Mark Symons
August 7, 2013, 9:14 PM

I get the WARN event::

46,000 events and counting! They occur in pairs every 360 seconds.

For me they are caused by the following applink setup:

Applink: Jenkins Plugin for JIRA v1.2.2
Connecting to: Jenkins v1.514
Running on: JIRA v5.2 (Applinks Plugin 3.10.4)

Honeywell JIRA Admin
October 21, 2013, 5:35 AM

This is happening in JIRA 6 a swell

Nicole Shepherd
November 21, 2013, 2:20 PM

Attaching our support zip as we are also experiencing this error.

Elena Vasilyeva
February 11, 2016, 3:55 AM

Hi, it's been a while since we've seen any activity on this one. So we are closing it according to the current policy regarding stale issues. Please, re-open it with a comment if you believe there is still work to be done.

Assignee

Unassigned

Reporter

JohnA

Labels

None

Add-on Type

None

Team

None

CC

None

Risk factor

None

QA Kickoff Status

None

QA Demo Status

None

Time tracking

0m

Time remaining

60h

Priority

Major
Configure