-
Notifications
You must be signed in to change notification settings - Fork 1
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
DA-311: Deploy as a Function #4
base: main
Are you sure you want to change the base?
Conversation
0faa6a2
to
8df6047
Compare
…ation + refactored main code
8df6047
to
c9e88a0
Compare
7aac1ac
to
496f0fe
Compare
eb577e4
to
595258f
Compare
This is the UI First line - heading Error label for this(by default when nothing is selected)-> Please specify a scope to which the function belongs. User should have Eventing Manage Scope Functions permission on this scope Second line - two horizontal dropdown boxes
Third line - heading Error label for this(by default when nothing is selected)-> Please specify a source location for your function. User should have DCP Data Read permission on this keyspace Fourth line - three horizontal dropdown boxes
Fifth line - heading Error label for this(by default when nothing is selected)-> Please specify a location to store Eventing data. User should have read/write permission on this keyspace Sixth line - three horizontal dropdown boxes
Seventh line - heading Eighth line - full line text box Error label depends on text box validation Ninth line - heading Tenth line - 1 drop down box with 2 options Eleventh line - heading Twelfth line - Text Area Thirteenth line - Openable Settings. Second line - dropdown menu Info label - below dropdown menu Third Line - heading Fourth line - dropdown menu Fifth Line - heading Sixth Line - text field Seventh line - heading Eighth line - dropdown menu Ninth Line - heading Tenth Line - text field Eleventh Line - heading Twelfth Line - text field Fourteen Line - Openable Settings. Here we can add any number of 3 types of binding types[from the dropdown menu(s)]. The dropdown menu contains: {
|
fe70c41
to
bf27a80
Compare
c85ff57
to
1bd6744
Compare
…context + introduced form validation and error generation
36ef2b1
to
e01bf00
Compare
d4d0529
to
3999c3a
Compare
Description
Whenever someone right-clicks on a .JS file in their project, add an option called “Deploy as a Couchbase Function“.
It should open a new dialog where you show the name of the cluster that it is currently connected to, and ask for the user to pick the bucket (select/combo component), and then pick the scope (Select/Combo component). When the user clicks on “ok“, you should call the following endpoint:
Full documentation here: Eventing REST API | Couchbase Docs under “Table 2. Eventing Functions API (advanced)“.
Validations: