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

tests(e2e): related objects working also for claims #4740

Merged
merged 1 commit into from
Oct 6, 2023

Conversation

phisco
Copy link
Contributor

@phisco phisco commented Oct 6, 2023

Description of your changes

Follow up to #4594 taking into account claims, which not being set as owners of the XR resulted in empty related objects, as you can see here.

I have:

  • Read and followed Crossplane's contribution process.
  • Added or updated unit and E2E tests for my change.
  • Run make reviewable to ensure this PR is ready for review.
  • Added backport release-x.y labels to auto-backport this PR, if necessary.
  • Opened a PR updating the docs, if necessary.

@phisco phisco requested a review from sttts October 6, 2023 10:00
@phisco phisco requested review from a team as code owners October 6, 2023 10:00
@phisco phisco requested review from bobh66 and pedjak October 6, 2023 10:00
@phisco
Copy link
Contributor Author

phisco commented Oct 6, 2023

I'm actually not sure I got the graph right, should we get the Claim's spec.resourceRef (XRC => XR) or the Composite Resource spec.claimRef (XR => XRC)? @sttts

@phisco
Copy link
Contributor Author

phisco commented Oct 6, 2023

Got my answer: https://github.com/crossplane/crossplane/actions/runs/6430195964/job/17460739141?pr=4740#step:12:492, it's the other way around, need to get spec.claimRef for composite resources.

Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com>
@phisco
Copy link
Contributor Author

phisco commented Oct 6, 2023

As you can see by the e2e failures it's now working fine 😅

@phisco phisco merged commit 78aa8d5 into crossplane:master Oct 6, 2023
14 of 16 checks passed
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.

None yet

3 participants