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

Client Encryption: Adds support to use gateway cache to get client encryption key properties #27210

Merged

Conversation

aayush3011
Copy link
Member

@aayush3011 aayush3011 commented Feb 18, 2022

Description

This PR brings in the support to carry out cached reads of client encryption key properties on the gateway cache. The gateway houses a cache for client encryption key properties to reduce throttling on master partitions.

Type of change

[] New feature (non-breaking change which adds functionality)

@ghost ghost added the Cosmos label Feb 18, 2022
@aayush3011 aayush3011 changed the title [TEMP] Encryption gateway cache changes Client Encryption: Adds support to use gateway cache to get client encryption key properties Mar 3, 2022
@aayush3011 aayush3011 marked this pull request as ready for review March 3, 2022 16:10
@check-enforcer
Copy link

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

Copy link
Member

@simplynaveen20 simplynaveen20 left a comment

Choose a reason for hiding this comment

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

LGTM , apart from some comments

@aayush3011 aayush3011 enabled auto-merge (squash) March 17, 2022 20:12
@aayush3011 aayush3011 merged commit 2d15741 into Azure:main Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants