Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[Website + Doc] generate connector configuration info automatically #14393

Closed
Anonymitaet opened this issue Feb 21, 2022 · 5 comments
Closed
Labels
doc Your PR contains doc changes, no matter whether the changes are in markdown or code files.

Comments

@Anonymitaet
Copy link
Member

When updating docs for #14383, @fantapsody suggests generating connector configuration tables automatically rather than updating them manually.

I've discussed w/ @urfreespace, he thinks it is workable. For example:

For the configuration table of the Elasticsearch sink connector, we can get this info from the source code file (ElasticSearchConfig.java)

image

One thing we need to consider is how to display the info.
@urfreespace believes we can generate independent web pages for each connector configuration info (as below), but it's too redundant to show all info connector configuration on the Pulsar home page. We need to figure out the best way to show the info.
image

Anyone would like to help? Thanks!

@github-actions
Copy link

The issue had no activity for 30 days, mark with Stale label.

@github-actions
Copy link

The issue had no activity for 30 days, mark with Stale label.

@tisonkun
Copy link
Member

tisonkun commented Dec 6, 2022

Closed as stale and no progress.

@tisonkun tisonkun closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
@Anonymitaet
Copy link
Member Author

Why close this issue? What are the criteria for keeping an issue open or closed?

@tisonkun
Copy link
Member

tisonkun commented Dec 7, 2022

@Anonymitaet Thanks for bubbling up this issue :)

I'll move this thread to the General discussion forum since there's no clear plan (how to implement it) or volunteers working on it.

@apache apache locked and limited conversation to collaborators Dec 7, 2022
@tisonkun tisonkun converted this issue into discussion #18776 Dec 7, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
doc Your PR contains doc changes, no matter whether the changes are in markdown or code files.
Projects
None yet
Development

No branches or pull requests

2 participants