-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Documentation #128
Comments
Perhaps should move plugin documentation requirements to a wiki page, thoughts @thibaultcha and @thefosk ? |
and
|
CLI API: Kong/docs.konghq.com#31. Which could also contain configuration (see the PR) |
This issue should probably be in getkong.org. Or closed and reopened as a smaller version there. |
This has been completed 👍 |
hutchic
pushed a commit
that referenced
this issue
Jun 10, 2022
### Summary #### libyaml 0.2.2 release - #95 -- build: do not install config.h - #97 -- appveyor.yml: fix Release build - #103 -- Remove unused code in yaml_document_delete - #104 -- Allow colons in plain scalars inside flow collections - #109 -- Fix comparison in tests/run-emitter.c - #117 -- Fix typo error - #119 -- The closing single quote needs to be indented... - #121 -- fix token name typos in comments - #122 -- Revert removing of open_ended after top level plain scalar - #125 -- Cherry-picks from PR 27 - #135 -- Windows/C89 compatibility - #136 -- allow override of Windows static lib name #### libyaml 0.2.3 release - #130 Fixed typo. - #144 Fix typo in comment - #140 Use pointer to const for strings that aren't/shouldn't be modified - #128 Squash a couple of warnings in example-deconstructor-alt - #151 Fix spelling for error message - #161 Make appveyor config be a hidden file - #159 Add CHANGES file - #160 Always output document end before directive (YAML 1.2 compatibility) - #162 Output document end marker after open ended scalars - #157 change cmake target name from libOFF.a to libyaml.a - #155 include/yaml.h: fix comments - #169 Fixed missing token in example - #127 Avoid recursion in the document loader. - #172 Support %YAML 1.2 directives - #66 Change dllexport controlling macro to use _WIN32
bungle
added a commit
that referenced
this issue
Nov 8, 2023
### Summary <a name="1.0.1"></a> #### [1.0.1] - 2023-11-07 ##### bug fixes - **jwk:** return error if exporting private key from public key ([#128](fffonion/lua-resty-openssl#128)) [3a1bc27](fffonion/lua-resty-openssl@3a1bc27) <a name="1.0.0"></a> #### [1.0.0] - 2023-11-03 ##### code refactoring - **\*:** remove unused cdefs [84abc0a](fffonion/lua-resty-openssl@84abc0a) - **\*:** BREAKING: drop OpenSSL 1.0.2, 1.1.0 and BoringSSL support [99b493e](fffonion/lua-resty-openssl@99b493e) ##### features - **fips:** add get_fips_version_text [935227b](fffonion/lua-resty-openssl@935227b) <a name="0.8.26"></a> #### [0.8.26] - 2023-10-30 ##### bug fixes - **version:** add support for all 3.x versions [1516b4d](fffonion/lua-resty-openssl@1516b4d) - **x509.csr:** remove extension before adding it [d6ed964](fffonion/lua-resty-openssl@d6ed964) Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
bungle
added a commit
that referenced
this issue
Nov 8, 2023
### Summary <a name="1.0.1"></a> #### [1.0.1] - 2023-11-07 ##### bug fixes - **jwk:** return error if exporting private key from public key ([#128](fffonion/lua-resty-openssl#128)) [3a1bc27](fffonion/lua-resty-openssl@3a1bc27) <a name="1.0.0"></a> #### [1.0.0] - 2023-11-03 ##### code refactoring - **\*:** remove unused cdefs [84abc0a](fffonion/lua-resty-openssl@84abc0a) - **\*:** BREAKING: drop OpenSSL 1.0.2, 1.1.0 and BoringSSL support [99b493e](fffonion/lua-resty-openssl@99b493e) ##### features - **fips:** add get_fips_version_text [935227b](fffonion/lua-resty-openssl@935227b) <a name="0.8.26"></a> #### [0.8.26] - 2023-10-30 ##### bug fixes - **version:** add support for all 3.x versions [1516b4d](fffonion/lua-resty-openssl@1516b4d) - **x509.csr:** remove extension before adding it [d6ed964](fffonion/lua-resty-openssl@d6ed964) Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Core
Plugins
Minimum required documentation for all plugins:
Name
Tagline
Installing
Configuration (including usage commands)
Usage (how it affects API(s) / Consumer(s), and examples of usage)
Examples of usage are for example take the
keyauth
plugin which adds authentication that can be used in multiple places such as theheader
,querystring
, orform
parameter:Using the
keyauth
plugin as aheader
:Where
key_name
is a value defined invalue.key_names
, andkey
is a key created with aPOST
request to/keyauth_credentials/
Explanation of each feature (how does
keyauth
differ frombasicauth
)The text was updated successfully, but these errors were encountered: