Skip to content

3.3.0-rc2

Pre-release
Pre-release
Compare
Choose a tag to compare
@tom-rm-meyer-ISST tom-rm-meyer-ISST released this 28 Aug 06:06
· 7 commits to main since this release
3.3.0-rc2
42ab830
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v3.3.0-rc2

The following Changelog lists the changes. Please refer to the documentation for configuration needs and understanding the concept changes.

The need for configuration updates is marked bold.

Added

  • Added unit tests Excel imports (#922)
  • Added role based permission handling for endpoints (#925)
  • Added Excel import page with template files download (#930)

Changed

  • Updated End-to-End tests to support local authentication (#920)
  • Update DemandAndCapacityNotification API to implement standard version 2.0 (#921)
  • Update Frontend Notification View with grouping based on disruptionId and seperating by status, forwarding connected notifications, editing and resolving notifications (#926)
  • CI: Trivy workflow should not fail if critical or high vulnerabilities are found (#948).

Fixes

  • Drop further security capabilities and apply default seccomp in chart's deployments (#938)

Chore

  • Updated open API (#929)
  • Updated dependencies to resolve high and critical security vulnerabilities (#932)
  • Updated User guide with the updated notification view and the new import page (#933)
  • Updated Arc42 documentation (#937)
  • Bump helm test workfow to new kubernetes version and latest q-gates puris version (#938)

Known Knowns

Upgradeability

Data base migrations are performed but assets.

Data Sovereignty

For productive use the following enhancements are encouraged

  • User FrontEnd available: Role Company Admin is able to query catalogue and see negotiations and transfers
    But company rules / policies need to be configured upfront in backend (via postman) to enable automatic contract
    negotiations, responsibility lies with Company Admin role
    --> add section in the User Manual describing this and the (legal) importance and responsibility behind defining these rules
  • Currently only one standard policy per reg. connector / customer instance is supported (more precisely one for DTR,
    one for all submodels), negotiation happens automatically based on this
    --> enhance option to select partner and define specific policies (to be planned in context of BPDM Integration)
    --> UI for specific configuration by dedicated role (e.g. Comp Admin) and more flexible policy configuration (withoutv code changes) is needed
  • As a non-Admin user I do not have ability to view policies in detail --> transparency for users when interacting with and requesting / consuming data via dashboard / views on underlying usage policies to be enhanced
  • ContractReference Constraint or configuration of policies specific to one partner only has notnot implemented --> clarification of potential reference to "PURIS standard contract" and enabling of ContractReference for 24.08.
  • unclear meaning of different stati in negotations --> add view of successfull contract agreeements wrt which data have been closed
  • current logging only done on info level --> enhance logging of policies (currently only available at debug level)
  • in case of non-matching policies (tested in various scenarios) no negotiation takes place --> enhance visualization or specific Error message to user
  • no validation of the Schema "profile": "cx-policy:profile2405" (required to ensure interop with other PURIS apps)

Styleguide

Overall

  • Brief description at the top of each page describing content would be nice for better user experience.

Catalog

  • No action possible -> unclear to user when and how user will consume an offer

Negotiations

  • Add filters for transparency (bpnl, state)
Assets 2
Loading