Problem
Refer to decision made in #1002
This feature request is to update GCP Pubsub channel
There re few more improvement to do while making this change:
/milestone v0.7.0
@Harwayne do you want me to give it a shot at this one?
Or you were planning on working on this for 0.7?
I'm not entirely sure all the changes it entails but I can start looking.
/assign @nachocano
Go for it!
This should also move to messaging.knative.dev as part of that work as per.
https://github.com/knative/eventing/blob/master/docs/decisions/eventing-and-messaging.md
Sounds good! Will do
On Wed, May 15, 2019 at 12:16 PM Ville Aikas notifications@github.com
wrote:
This should also move to messaging.knative.dev as part of that work as
per.https://github.com/knative/eventing/blob/master/docs/decisions/eventing-and-messaging.md
—
You are receiving this because you were assigned.Reply to this email directly, view it on GitHub
https://github.com/knative/eventing/issues/1214?email_source=notifications&email_token=ABD65DBFLMDPHDSOAIM74ODPVRORNA5CNFSM4HMGNQJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVPVPZQ#issuecomment-492787686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABD65DF7UJ3HSL5COEPHF5TPVRORNANCNFSM4HMGNQJA
.
@Harwayne @vaikas-google @evankanderson
I'm starting to look at this, and there is this old proposal of also renaming gcppubsub to google-cloud-pubsub or maybe cloud-pubsub. I don't think the latter one is appropriate though. But if we are planning on renaming, this might be the right time.
Would you guys be OK to rename it to google-cloud-pubsub? Or maybe some other name?
I actually think it would be a good idea to do the renaming. This will make it easier for backwards compatibility with the other provisioner-based one. We mark gcppubsub as deprecated in 0.7, and remove it entirely in 0.8.
I think google-cloud-pubsub or google-pubsub would be good. cloud-pubsub seems not clear enough.
google-cloud-pubsub aligns with the brand name.
On Wed, May 15, 2019 at 5:33 PM Ville Aikas notifications@github.com
wrote:
I think google-cloud-pubsub or google-pubsub would be good. cloud-pubsub
seems not clear enough.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knative/eventing/issues/1214?email_source=notifications&email_token=AKYQBFCHMZQFUAC5BEVKTHTPVSTXJA5CNFSM4HMGNQJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQKE4Q#issuecomment-492872306,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKYQBFERW2ZHG6RTKT5A6C3PVSTXJANCNFSM4HMGNQJA
.
--
Regards,
Akash
Cool! I already started the code with that one. google-cloud-pubsub it is!
On Wed, May 15, 2019 at 8:05 PM Akash Verenkar notifications@github.com
wrote:
google-cloud-pubsub aligns with the brand name.
On Wed, May 15, 2019 at 5:33 PM Ville Aikas notifications@github.com
wrote:I think google-cloud-pubsub or google-pubsub would be good. cloud-pubsub
seems not clear enough.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/knative/eventing/issues/1214?email_source=notifications&email_token=AKYQBFCHMZQFUAC5BEVKTHTPVSTXJA5CNFSM4HMGNQJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQKE4Q#issuecomment-492872306
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AKYQBFERW2ZHG6RTKT5A6C3PVSTXJANCNFSM4HMGNQJA.
--
Regards,
Akash—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/knative/eventing/issues/1214?email_source=notifications&email_token=ABD65DAPETNTBUOE3PP4WWLPVTFRHA5CNFSM4HMGNQJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQQT6I#issuecomment-492898809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABD65DCE6UW3BEL3324SAELPVTFRHANCNFSM4HMGNQJA
.
Stopping this as @n3wscott wants to drive it outside our knative-eventing repo. Go for it!
/assign @n3wscott
/unassign @nachocano
I am looking forward to see this. This should be "multi-tenant" in the sense that a user with no privilege in knative-* namespaces should be able to use this CRD in his/her own namespace using a private service account key and project.
This is being worked on in the https://github.com/google/cloud-run-events repo, but it's not ready yet.
/milestone v0.8.0
/milestone v0.7.0
@adrcunha: You must be a member of the knative/knative-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.
In response to this:
/milestone v0.7.0
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
This is being worked on in the https://github.com/google/cloud-run-events repo, but it's not ready yet.
I assume this is a private repo , it gives a 404 !!
This is being worked on in the https://github.com/google/cloud-run-events repo, but it's not ready yet.
I assume this is a private repo , it gives a 404 !!
Sorry, typo in the repo name. The correct one is: https://github.com/GoogleCloudPlatform/cloud-run-events
/close
@n3wscott: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.