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

Fix kafka input clusterName #1620

Closed
wants to merge 1 commit into from

Conversation

haorenfsa
Copy link
Contributor

Signed-off-by: shaoyue.chen [email protected]

Description of your changes

A follow-up of #1612

The external-name should be the uniq id of the resource. Usually we use the Arn of the resource provided by AWS.
The ClusterName is the user defined name. Which is currently not offered in parameters. It's reasonable to use the name of CR as the ClusterName.

Fixes #1611

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Signed-off-by: shaoyue.chen <[email protected]>
@abrarcci
Copy link

abrarcci commented Jan 6, 2023

Could we get an approval on this one please? Many Thanks

@haorenfsa
Copy link
Contributor Author

@haarchri take a look?

@haarchri
Copy link
Member

haarchri commented Jan 8, 2023

I will take a look but cr.name we normally Not using - i guess the original problem is around the initializer

@haorenfsa
Copy link
Contributor Author

haorenfsa commented Jan 8, 2023

The key is that we need a clusterName for the createCluster input, but the Parameters struct for Cluster.kafka does not provide it.
So I think we've got 2 choices:

  1. Use the CR name
  2. Add ClusterName in Parameters

@haarchri
Copy link
Member

haarchri commented Jan 8, 2023

created the following PR #1624 - the problem is when we using cr.name directly - people using compositions and the cr.name is generated per default - so its better to use clusterName in spec

@haorenfsa
Copy link
Contributor Author

created the following PR #1624 - the problem is when we using cr.name directly - people using compositions and the cr.name is generated per default - so its better to use clusterName in spec

Good point. I agree with u. I'll close this.

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.

Cluster.kafka cannot be created
3 participants