feat: add org propagation [ZEN-340]

[patricia-v]

Jira ticket: ZEN-340

Related PRs

deeproxy#211
registry#29177

Context

Since the introduction of the new services, we started fetching the org's FFs in registry when deeproxy performs a token validation to its endpoint. Previously, this operation did not require the current org, so the default one was used by registry.

We currently want the FFs of the org being used, so we need to propagate the org provided in CLI by either the flag or the config.

Relevant code-client requests to propagate the org

From my investigation, it seems that the only code-client requests performed by CLI that triggers a token verification are:

• createBundle()
• checkBundle()
• extendBundle()
• getAnalysis()

The last one, getAnalysis(), already had the proper relay of the org, so the only change necessary was adding the header for deeproxy.

The flows (and changes) for the requests are simplified in the following diagrams:

TODO

• Tests
• Update CLI to use latest version of code-client (after merge)

[ghost]

This PR modifies files linked to issues tracked in Stepsize. You might want to review their status, priority, and scope.

duplicate arguments for analysis context

• src/interfaces/analysis-options.interface.ts

Interfaces can easily go out of sync

• src/interfaces/analysis-options.interface.ts

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

[ghost]

This PR modifies files linked to issues tracked in Stepsize. You might want to review their status, priority, and scope.

duplicate arguments for analysis context

• src/interfaces/analysis-options.interface.ts

Interfaces can easily go out of sync

• src/interfaces/analysis-options.interface.ts

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

[snyksec]

🎉 This PR is included in version 4.13.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀