Setting TLS1.2 as min for cosmosDB #3520
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
sankur-codes
requested review from
jewzaam,
bennerv,
hawkowl,
rogbas,
jharrington22,
cblecker,
cadenmarchese,
UlrichSchlueter,
s-amann,
SudoBrendan,
Shivkumar13,
yjst2012,
jaitaiwan,
anshulvermapatel,
hlipsig,
dofinn and
tiguelu
as code owners
sankur-codes
added
ready-for-review
priority-high
sankur-codes
changed the title
|
/azp run ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mociarain
reviewed
Apr 24, 2024
hlipsig
approved these changes
Apr 24, 2024
cadenmarchese
added a commit
that referenced
this pull request
May 1, 2024
This reverts commit e1b8a4e.
sankur-codes
changed the title
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.
Which issue this PR addresses:
Fixes ARO-6842
What this PR does / why we need it:
This PR set TLS 1.2 as minimum requirement for cosmosdb as required by Microsoft Compliance
Test plan for issue:
Tested using full-rp-dev-setup. Details added in JIRA ticket.
Is there any documentation that needs to be updated for this PR?
NA
How do you know this will function as expected in production?
Tested using full-rp-dev-setup. Details added in JIRA ticket.