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

Allow both resource claims and managed resources to pass the class kind predicate #18

Merged
merged 2 commits into from
Sep 13, 2019

Conversation

negz
Copy link
Member

@negz negz commented Sep 13, 2019

Description of your changes

It turns out both our watches use the same predicate and apply it to the watched kind, not the kind that actually gets enqueued.

Checklist

I have:

  • Run make reviewable to ensure this PR is ready for review.
  • Ensured this PR contains a neat, self documenting set of commits.
  • Updated any relevant documentation, examples, or release notes.
  • Updated the RBAC permissions in clusterrole.yaml to include any new types.

Signed-off-by: Nic Cope <negz@rk0n.org>
It turns out both our watches use the same predicate and apply it to the watched
kind, not the kind that actually gets enqueued.

Signed-off-by: Nic Cope <negz@rk0n.org>
@negz negz requested a review from hasheddan September 13, 2019 07:02
@negz
Copy link
Member Author

negz commented Sep 13, 2019

I've also run make tests

@negz
Copy link
Member Author

negz commented Sep 13, 2019

Confirmed this works by building stack-gcp against this commit and creating a RedisCluster, RedisClusterClass, and CloudSQLInstanceClass. The binding happens as soon as the managed resource becomes available, as expected.

@negz negz merged commit 0aee6ee into crossplane:master Sep 13, 2019
@negz negz deleted the youshallnotpass branch September 13, 2019 08:07
negz added a commit to negz/provider-gcp that referenced this pull request Sep 13, 2019
We want the fix from crossplane/crossplane-runtime#18

Signed-off-by: Nic Cope <negz@rk0n.org>
@jbw976
Copy link
Member

jbw976 commented Sep 13, 2019

Thank you for finding this issue and getting it fixed so quickly @negz!! 🙇

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