Adding public namespace to sessionResolver; Respond B2B impersonate a…

[wender]

What problem is this solving?

B2B impersonation don't require Admin Access / LM Call Center Operator This change makes the directive withCurrentProfile consider B2B impersonation as CallCenterOperator when responding for userType

How to test it?

Access this workspace Login using [email protected] and Vtex1234

Using GraphiQL IDE, select storefront-permissions app run this mutation

mutation {
  impersonateUser(userId: "1820b65a-a8e8-418d-9c38-c755e015e22c") {
    message
    status
  }
}

Refresh the site to apply the sessions, navigate to my account > profile

Screenshots or example usage:

Without the change

With the change

[vtex-io-ci-cd[bot]]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• [x] Patch (backwards-compatible bug fixes)

• [ ] Minor (backwards-compatible functionality)

• [ ] Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• [ ] No thanks, I would rather do it manually 😞

[vtex-io-docs-bot[bot]]

Beep boop :robot:

I noticed you didn't make any changes at the docs/ folder

• [x] There's nothing new to document :thinking:
• [ ] I'll do it later :disappointed:

In order to keep track, I'll create an issue if you decide now is not a good time

• [ ] I just updated :tada::tada:

[rafael-marques]

Hi, @wender @victorhmp @igorbrasileiro do you guys have an idea when this will be published to prod? Thanks :)

[vtex-io-ci-cd[bot]]

Your PR has been merged! App is being published. :rocket: Version 2.161.2 → 2.161.3

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. :book: