-
Notifications
You must be signed in to change notification settings - Fork 61
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
Alias argument for confluent_subject_config resource #350
Comments
Thank you for creating this issue @AS-auxmoney! Could you also share an example of you you'd want it to look like in TF? |
Hi @linouk23, thanks for the fast response. I guess something like this:
|
@linouk23 Btw, are you open to contributions? I have already implemented some features for another provider (with another github account, this is my work account), therefore I am quite confident about this feature. |
@AS-auxmoney all contributions are very welcome! I've got a quick question: Is this |
@linouk23 To my knowledge, it is only available through the SR API and not at all through CLI or UI:
And there is no way to look up all existing alias, it is only possible to look up, if a specific alias exist. |
Nice! As long as it's available in the API, we can definitely add it to |
@linouk23 I got a deeper look into this matter and this is way more complicated than expected. The problem: You are not supposed to set an alias on an existing subject, but you are supposed to set an alias and reference it to the existing subject. Example:
Wrong:
Correct:
Only then the same is returned in both cases
So, lets come to the actual problem. The ccloud SDK is implemented in the wrong way for the alias feature. When naively using |
Please add the alias argument to the resource confluent_subject_config, so it will be possible to define aliases for schema subject names. See https://docs.confluent.io/platform/current/schema-registry/fundamentals/index.html#subject-aliases for details.
If welcomed, I can work on a pull request.
The text was updated successfully, but these errors were encountered: