-
Notifications
You must be signed in to change notification settings - Fork 70
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
For non-cloud plugin settings, set hosting property to on-prem
#269
Changes from all commits
26ed4d7
9d6c4bd
9d53d19
9b20aa1
3f3ac4d
39cc185
9c209de
4ec789c
479f2a6
47c3c39
f16e3ee
f3040c9
b862b40
d96e3c3
9b30053
285d273
807b173
a972511
f84bb01
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -47,7 +47,8 @@ | |
"type": "bool", | ||
"help_text": "When true, OAuth will be used as the authentication means with Zoom. \n When false, JWT will be used as the authentication means with Zoom. \n If you're currently using a JWT Zoom application and switch to OAuth, all users will need to connect their Zoom account using OAuth the next time they try to start a meeting. [More information](https://mattermost.gitbook.io/plugin-zoom/installation/zoom-configuration).", | ||
"placeholder": "", | ||
"default": false | ||
"default": true, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just double checking this default value change is intended. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @larkox Yes it's intended, since the OAuth feature is now our "main" feature offering, and we want to discourage using the JWT method. |
||
"hosting": "on-prem" | ||
}, | ||
{ | ||
"key": "AccountLevelApp", | ||
|
@@ -88,15 +89,17 @@ | |
"type": "text", | ||
"help_text": "The API key generated by Zoom, used to create meetings and pull user data.", | ||
"placeholder": "", | ||
"default": null | ||
"default": null, | ||
"hosting": "on-prem" | ||
}, | ||
{ | ||
"key": "APISecret", | ||
"display_name": "API Secret:", | ||
"type": "text", | ||
"help_text": "The API secret generated by Zoom for your API key.", | ||
"placeholder": "", | ||
"default": null | ||
"default": null, | ||
"hosting": "on-prem" | ||
}, | ||
{ | ||
"key": "WebhookSecret", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is commented out to support compiling the plugin with an "unknown" property on the plugin settings. Updating the server version to otherwise support this is not trivial because:
golang:1.18-node
image also updates the node version, making it so it is a newer version than this plugin currently compiles withThe reason for this
DisallowUnknownFields
call is to prevent the manifest field structure from being out of sync, which is something that's occurring in this PR. We are purposely "breaking the rules here", while the circleci update is still underway.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @hanzei for discussion on this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Details on the error I was getting in CI mattermost/circleci-orbs#29 (comment)