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

Proposal: Introduce a "public" top-level package directory for sharing outside #889

Closed
rhuss opened this issue Jun 16, 2020 · 10 comments
Closed
Assignees
Labels
kind/refactor Code refactor needed triage/accepted Issues which should be fixed (post-triage)

Comments

@rhuss
Copy link
Contributor

rhuss commented Jun 16, 2020

One design goal of kn was also to expose a public API to offer common client functionality to other go based applications. We already have some of those API hooks but at various places:

  • The client API interfaces at
    • pkg/serving/v1
    • pkg/sources/v1alpha2
    • pkg/eventing/v1beta1
  • A testing lib for E2E tests in
    • lib/test
  • Utilities for parsing kn flags
    • pkg/kn/flags

This proposal suggests introducing a top-level package under which all externally shared code is collected.

This could be either the already exposed lib or maybe something more explicit like public.
Also, a CI test should check for whether any file of this directory is touched and raise some awareness (like an extra label) that a review should check for any backward compatibility issues.

Please add a 👍 for being positive for this change, 👎 if you against it.

@rhuss
Copy link
Contributor Author

rhuss commented Jun 26, 2020

ballot is over, all positive. Thanks !

/assign rhuss

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 15, 2020
@rhuss
Copy link
Contributor Author

rhuss commented Oct 21, 2020

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2020
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2021
@rhuss
Copy link
Contributor Author

rhuss commented Jan 20, 2021

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2021
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2021
@dsimansk
Copy link
Contributor

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2021
@rhuss
Copy link
Contributor Author

rhuss commented Jul 9, 2021

@dsimansk I think we can close this issue but use it as an input for the new shared pkg repo structure ?

@rhuss rhuss added triage/accepted Issues which should be fixed (post-triage) kind/refactor Code refactor needed labels Jul 9, 2021
@dsimansk
Copy link
Contributor

dsimansk commented Jul 9, 2021

@rhuss yep, works for me.

@rhuss
Copy link
Contributor Author

rhuss commented Jul 9, 2021

Closing this and track it in #1039

@rhuss rhuss closed this as completed Jul 9, 2021
mgencur pushed a commit to openshift-knative/client that referenced this issue Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/refactor Code refactor needed triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

No branches or pull requests

3 participants