Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Cred Scan] Generate fake key instead of putting directly in the test file #16700

Merged
merged 4 commits into from
Aug 2, 2021

Conversation

HarshaNalluru
Copy link
Member

@HarshaNalluru HarshaNalluru commented Aug 2, 2021

This would help reduce the noise in the cred scan report by striking off one complaint from the list of complaints.

https://dev.azure.com/azure-sdk/internal/_build?definitionId=1394&_a=summary

@ghost ghost added the Event Grid label Aug 2, 2021
@HarshaNalluru HarshaNalluru marked this pull request as ready for review August 2, 2021 19:19
Copy link
Member

@ellismg ellismg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Sorry this was causing cred scan noise, this a clever fix!

@HarshaNalluru HarshaNalluru enabled auto-merge (squash) August 2, 2021 20:05
@HarshaNalluru HarshaNalluru merged commit c8756d9 into Azure:main Aug 2, 2021
@HarshaNalluru HarshaNalluru deleted the harshan/credscan-fix branch August 3, 2021 00:49
ellismg added a commit to ellismg/azure-sdk-for-js that referenced this pull request Aug 3, 2021
In Azure#16700 we updated our tests to generate the key we used for testing
by doing a base64 conversion of a fixed string so we didn't have something that looked like a key embeded in source which was upsetting some static analysis tools.

This casues a build break in the min/max testing where `btoa` can't be found when building the test. Since we have the correct runtime behavior in the test to only call `btoa` when we are not in a node-context we simply reference the dom library to appease the compiler.
ellismg added a commit that referenced this pull request Aug 4, 2021
In #16700 we updated our tests to generate the key we used for testing
by doing a base64 conversion of a fixed string so we didn't have something that looked like a key embeded in source which was upsetting some static analysis tools.

This casues a build break in the min/max testing where `btoa` can't be found when building the test. Since we have the correct runtime behavior in the test to only call `btoa` when we are not in a node-context we simply reference the dom library to appease the compiler.
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this pull request Nov 9, 2021
Move swagger json file out of definitions folder (Azure#16700)

* IoT Central Public API 1.1-preview Oct Release (Azure#16514)

* Add new 2.0-preview.1 version for IoT Central

* fix typo on enum value

* rollback 1.0 changes, applied 2.0-preview.1

* fix typo

* remove non-used examples

* fix style

* update version from 2.0-preview.1 to 1.1-preview

* update code review comments, fix patch consumes with json-patch support, fix examples for fileupload

* add nextLink to collection of orgs

* fix typo

* fix wrong position of paging

* fix the paging

* add . to description

* update default to use enum for api-version

* add oct release with query, cde v2, device filter, device template filter, relationship, edge template, simplified template patching

* update examples

* fix lint error, model validation

* fix missing type in examples, remove url format

* fix ID case

* fix id case

* fix ID case

* add iotc query language reference

* fix typo

* Move things out of definitions

* remove ../

Co-authored-by: Johnson Yang <hayang@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants