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

Use Generation instead of ResourceVersion when computing the cache key #1244

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

ulucinar
Copy link
Collaborator

@ulucinar ulucinar commented Mar 28, 2024

Description of your changes

The provider cache manager currently uses ProviderConfig.ResourceVersion when computing the cache keys. This PR changes it to ProviderConfig.Generation so that only ProviderConfig's spec updates will invalidate cache entries.

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable to ensure this PR is ready for review.
  • Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Validated the PR using the package index.docker.io/ulucinar/provider-aws-iam:v1.3.0-8dbbc58fbd82da76ef5f8f50c34aa75494964bbd and by modifying the spec of the ProviderConfig. Also via uptest here: https://github.com/crossplane-contrib/provider-upjet-aws/actions/runs/8470828375

Signed-off-by: Alper Rifat Ulucinar <ulucinar@users.noreply.github.com>
@turkenf
Copy link
Collaborator

turkenf commented Mar 28, 2024

/test-examples="examples/rds/v1beta1/clusterroleassociation.yaml"

Copy link
Collaborator

@turkenf turkenf left a comment

Choose a reason for hiding this comment

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

Thank you @ulucinar, LGTM.

@ulucinar ulucinar merged commit 053d318 into crossplane-contrib:main Mar 28, 2024
12 checks passed
@ulucinar ulucinar deleted the fix-cache-key branch March 28, 2024 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants