Build forked dex in the plan file #6085

kalroy · 2021-11-10T15:56:38Z

Signed-off-by: Kallol Roy karoy@progress.com

🔩 Description: What code changed, and why?

There is a need to validate the request id before we query the DB.
This requires us to make the changes in dex code base which is a third party code.
The process to make the change in the third party code and getting a merge approval can be troublesome and time consuming.
Hence the repo is forked and the changes are made in a branch on dex 2.27 version.
https://github.com/chef/dex-1/tree/add_request_validators

This PR is to make changes in the plan file to pull the code from the branch and build it.

⛓️ Related Resources

👍 Definition of Done

The PR needs to be approved though not merged Add request validators dex-1#4
The dex should invalidate requests with invalid auth code

👟 How to Build and Test the Change

hab studio enter
rebuild components/automate-dex
Check the UI or make dex api calls as mentioned in the issue https://a2-dev.test/dex/approval?req=req=etsk5jfjfq2ao7s2pfthls72m%20HTTP/1.1

✅ Checklist

All PRs must tick these:

I have read the CONTRIBUTING document.
All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)