You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding private properties to policy definition entity.
General information
Extending policy definition entity with the map privateProperties. Additionally, adjust the affected transformers, search in privateProperties and policy definition API managements accordingly. The functionality would support in-memory and postgres as a store.
Adoption level
Next, please tell us what level of adoption you intend to provide. (pick only one)
Reference a feature as "friend"
[ X] Incorporate a feature as core EDC component
Adoption in EDC core
If you chose to add your feature as a core EDC component, please answer the following questions.
Why should this contribution be adopted?
This feature is similar to what is currently available for Asset entity. Therefore, the required contribution for the policy definition to enable the private properties looks very similar.
Could it be achieved with existing functionality? If not, why?
No. This is a completely new field withing the policy definition entity.
Are there multiple use cases or applications who will benefit from the contribution?
Yes, same as Asset entity.
Can it be achieved without introducing third-party dependencies? If not, which ones?
Yes
Would this feature limit platform independence in any way? If so, how and why?
No.
Is it going to be a self-contained feature, or would it cut across the entire code base?
Adoption Request
Adding private properties to policy definition entity.
General information
Extending policy definition entity with the map privateProperties. Additionally, adjust the affected transformers, search in privateProperties and policy definition API managements accordingly. The functionality would support in-memory and postgres as a store.
Adoption level
Next, please tell us what level of adoption you intend to provide. (pick only one)
Adoption in EDC core
If you chose to add your feature as a core EDC component, please answer the following questions.
Why should this contribution be adopted?
This feature is similar to what is currently available for Asset entity. Therefore, the required contribution for the policy definition to enable the private properties looks very similar.
Could it be achieved with existing functionality? If not, why?
No. This is a completely new field withing the policy definition entity.
Are there multiple use cases or applications who will benefit from the contribution?
Yes, same as Asset entity.
Can it be achieved without introducing third-party dependencies? If not, which ones?
Yes
Would this feature limit platform independence in any way? If so, how and why?
No.
Is it going to be a self-contained feature, or would it cut across the entire code base?
a self-contained feature.
Reference items:
#2592 (reply in thread)
The text was updated successfully, but these errors were encountered: