Configure WhiteSource Bolt for GitHub #173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mend-bolt-for-github[bot]](https://avatars.githubusercontent.com/in/16809?s=60&v=4){kind=small}
gagaboy
added a commit
to gagaboy/moqui-runtime
that referenced
this pull request
Jan 31, 2022
* commit '05f8e8e55895495c1a8e79e34563a89ed159841d': (34 commits) On DataExport screen handle entityNames parameter that is a comma separated string which happens in qapps, fixes latest issue with DataExport under qapps/qvt Fixed the problem that moqui cannot be deployed as non-root webapp in Tomcat (moqui#190) On DataImport screen add support for creating missing records, with warnings about incomplete PKs because they can cause duplicate records; on a side note this screen is now a good way to test data for incomplete PKs Some improvements to Data Check functionality on the Data Import screen, shows check results in a table and allows selective update of field values; a first pass on this, another thing to handle that isn't there yet is adding missing records though that can be done with existing add missing functionality, just not selectively within a file On UserGroupDetail add new UserGroupPreference.groupPriority field to add/update group pref forms Added a new column for linking to auto screen. (moqui#188) On System/dashboard screen add a try/catch to handle errors getting ES cluster info, found this to break the whole page when ES is down MFA REST API and Login screen improvements (moqui#187) Update Swagger UI to 4.1.3 with JS/CSS files loaded from cdnjs instead of locally to avoid having files in the repos making it easier to update over time, along with cleaning up an old mess and a few CVE and WS security issues: moqui#176, moqui#177, moqui#178, moqui#179, moqui#180, moqui#181, moqui#182, moqui#183, moqui#184, moqui#185, moqui#186 Add .whitesource configuration file (moqui#173) BugFix date-find can not select date from calendar. (moqui#174) Remove empty lines before <!doctype html>, now it become the first line. (moqui#175) In qvt render mode m-text-line VueJS component add reverseFillMask prop, in qvt text-line macro if field has the number validation class then set reverse-fill-mask In Login.xml specify in-map for call to reset#Password service so that other parameters cannot be specified as url parameters/etc Removed unused code from last commit to System/dashboard for Request Details dialog Add Request Details dialog to System/dashboard for inspecting headers, etc; change /status transition in webroot.xml to use ec.user.getClientIp() to use client ip header settings to avoid X-Forwarded-For spoof Misc improvements suggested by Arzang Kasiri: in WebrootVue.qvt.js m-display preserve whitespace in output by using the quasar q-input autogrow option; show the current date/time in system default time zone on System/dashboard; on AutoFind do a count query and only require parameters if table has more than 1 million records Add new targetPath field to EntitySyncDetail screen Use new getStatusMap(true) variation now support in ECFI in moqui-framework In DataExport screen add CSV support, in DataSnapshot screen add CSV and JSON support and commented fields for isoDateTime and tableColumnNames, currently commented because they are only supported for CSV and not XML or JSON yet ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to WhiteSource Bolt for GitHub! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.
🚦 WhiteSource Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable WhiteSource Bolt for GitHub, simply close this Pull Request.
What to Expect
This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, WhiteSource Bolt for GitHub will use the default configuration.
Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource Bolt for GitHub will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.
If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.
❓ Got questions? Check out WhiteSource Bolt for GitHub docs.
If you need any further assistance then you can also request help here.