Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[POLICY_STORE] No movement of policyId from one BPNL to other BPNL in case of Update #560

Open
3 tasks
mkanal opened this issue Apr 24, 2024 · 1 comment
Open
3 tasks
Labels
BLOCKED Items which are blocked by dependencies policy_store Issues regarding the IRS policy store.

Comments

@mkanal
Copy link
Contributor

mkanal commented Apr 24, 2024

As user
I want that policyId is not moved from one BPNL to other BPNL in case of update PUT
so that there is a stable behavior of the api and no confusion for the user

Link

Hints / Details

  • ...

Acceptance Criteria

  • In the case of an update of a policyId to a new BPNL collection, the policyId should not be removed from the old BPNL.
  • Add Int tests for this function
  • Extend test cases

Out of Scope

  • ...
@mkanal mkanal added this to IRS Apr 24, 2024
@github-project-automation github-project-automation bot moved this to inbox in IRS Apr 24, 2024
@mkanal mkanal added the policy_store Issues regarding the IRS policy store. label Apr 24, 2024
@mkanal mkanal added the BLOCKED Items which are blocked by dependencies label Apr 29, 2024
ds-jhartmann added a commit to ds-jhartmann/item-relationship-service that referenced this issue Jun 13, 2024
…-helm-release6.7.1

Chore/prepare helm release6.7.1
@mkanal
Copy link
Contributor Author

mkanal commented Jun 21, 2024

Blocked by #561

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BLOCKED Items which are blocked by dependencies policy_store Issues regarding the IRS policy store.
Projects
Status: inbox
Development

No branches or pull requests

1 participant