-
Notifications
You must be signed in to change notification settings - Fork 1
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
PIN-5555 eservice delegateClientAccess #1193
PIN-5555 eservice delegateClientAccess #1193
Conversation
ffee648
to
0f7ec96
Compare
…b.com/pagopa/interop-be-monorepo into feature/eservice-clientdelegable-PIN-5555
…b.com/pagopa/interop-be-monorepo into feature/eservice-clientdelegable-PIN-5555
…rvice-clientdelegable-PIN-5555
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left the same comments I left on #1188, furthermore for this PR I would investigate what happens in case of the two updates (eservice draft and after the publication of the eservice). Since the flag isDelegable
is editable in both cases, we shall define what happens to this flag and why it shall not be editable if the other is editable
2dad452
to
242a9f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 just one super minor comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving the same comment I left in #1188 👇
Three things are still missing IMO:
- Adding the flag into the various read calls in BFF and API GW (only the ones that don't return compact data)
- Adding the flag into the eservice import/export in BFF (see fileUtils.ts)
- Updating the corresponding Bruno calls, performing some manual tests, and adding some test screenshots to the PR
You can use #1109 as a reference for all the points, where I did the same for the isSignalHubEnabled
flag.
…rvice-clientdelegable-PIN-5555
…rvice-clientdelegable-PIN-5555
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
I would also add a couple of new tests to test the create/update cases where:
- the new flag is set to some value X
- the isDelegable flag is false/undefined
In these cases we shall test that in the eservice the new flag is set to false/undefined, the value of isDelegable, and the value X from the seed is ignored
…p-be-monorepo into feature/eservice-clientdelegable-PIN-5555
Don't merge before #1188
POST eservice:
GET Eservice:
Eservice su mongo:
update eservice:
GET con flag updated:
producer eservice: