Solved: Access a property set in a shared flow - Page 2

danielfrancisco · 05-27-2021 04:46 AM

Hi,

We've extracted some common logic which is reused across different proxies to a shared flow. This shared flow access certain configuration in a property set. This configuration does not change between proxies, so the properties file lives in the shared flow bundle, or at least that was our intention. The reality is that this doesn't work, and a policy in the shared flow can only read a property set in the actual proxy, thus forcing us to replicate the property set, which doesn't change, across all proxies that use the shared flow.

Is this by design? Is it a bug? Wouldn't be more appropriate if this worked in a hierarchical way in which the property set could live in the shared flow but, if also present in the proxy, the property values get overridden by the ones in the property set that lives in the proxy?

Thanks.

dchiesa1

From the description you provided, it sounds like it's both "by design" and "a bug", a design bug.

Wouldn't be more appropriate if this worked in a hierarchical way in which the property set could live in the shared flow but, if also present in the proxy, the property values get overridden by the ones in the property set that lives in the proxy?

That's an interesting idea. We'll need to discuss this.

In the meantime, you have a workaround: store the propertyset at the Environment-scope. In that case, a sharedflow can reference the propertyset.

To distinguish the configuration for the shared flow from the configuration for other things, You can either

use a specific name for the propertyset, for this sharedflow.
Use a specific set of keynames in the propertyset for this sharedflow

View solution in original post