Test and verify, then update documentation, if dependency scanning works with jfrog npm proxy
Problem to solve
My customer had a question on dependency scanning jobs and authenticating with non-Maven private proxies - They have a JFrox NPM proxy that needs auth and is wondering if we have an example of somebody bootstrapping yarn creds with a before_script?
we should verify, and we should update our documentation.
Intended users
Further details
Proposal
Permissions and Security
Documentation
Availability & Testing
This issue ticket itself looks to be a manual test
- Ensure that the airgap demo system is up and running, engineer and SET can work together if it is down
- Add
jfrox npm proxy
to the airgapped demo system - Manually verify functionality, documentation to be updated
- Verify documentation steps provide a workable solution
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Olivier Gonzalez