Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

In the OpenAPI spec, section "Link Object",
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#linkObject

the "Examples" table following after the text
"The table below provides examples of runtime expressions and examples of their use in a value:"

contains a confusing "note" in the third row, and I think a "note" is missing in the second row.

Proposed changes:

Hello,

Im new with node, its possible to you improve instalation docs for 'standalone' server installation ?

How to install latest node, npm, and dependencie to run n8n with

npm install n8n -g

example: im running ubuntu 16.04.

It was non-obvious to me that the parameters supplied to the model via the withTransformerParameter would be under a "parameters" key rather than the raw key supplied in the DSL call. I think it would be helpful to have an explicit example in addition to the several request based examples.

I'm happy to raise a PR to the docs if this seems like a good idea.

Right now Node.js's README writes:

var client = foo.bar({
  username: 'pksunkara',
  password: 'password'
});

Is it possible to change it to:

var client = foo.bar({
  username: 'api_key',
  password: 'api_secret'
});

Provide a mock show page that will allow users to view a mock configuration with a legit layout.

• Use code formatting for body content & script
• Description links should be rendered as link, not as text

The hard 100 request (POST/PUT/GET/etc) limit should be more prominently called out in docs.

Line 172 from https://github.com/Mashape/mockbin/blob/master/docs/api/bins.md reads:

All requests to Bin will be logged for later inspection (max of 100 requests)

On a personal project I must have missed that line and burned myself because I thought there was an internal application/ne

Summary

The initial implementation is missing the following features:

1. %START_TIME% commands ignore the user-defined format string
2. %DYNAMIC_METADATA(NAMESPACE:KEY*):Z% commands return a stub value
3. %FILTER_STATE(KEY):Z% commands return a stub value

In the Transform Tree example here
https://glom.readthedocs.io/en/latest/snippets.html#transform-tree

the code uses Ref

"With an arbitrary depth tree, Ref can be used to express a recursive spec."

and gives a code example

etree2tuples = Fill(Ref('ElementTree', (T.tag, Iter(Ref('ElementTree')).all())))

I'm using glom 19.10.0 and it doesn't come with Ref

from glom 

Summary

Kong Ingress Controller touches all ingresses, regardless of "kubernetes.io/ingress.class".

Kong Ingress controller version
0.7.0 (with 0.7.1 is the same)

Kong or Kong Enterprise version
1.4 (I tried also 1.5.0)

Kubernetes version

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89",

Hi there! I wanted to propose adding the following badge to the README to indicate how many TODO comments are in this codebase:

The badge links to tickgit.com which is a free service that indexes and displays TODO comments in public

I'm looking for any documentation that provides more information or recommendations on managing the Nakadi platform in a production environment.

• High-available setup
• Capacity management
• Backup/restore strategies
• Release management (upgrade strategy)

Is there any community forum to discuss the Nakadi platform?

Description:

Following error is logged during startup, after changing the userstore type as database in deployment.toml.

org.wso2.carbon.databridge.agent.exception.DataEndpointLoginException: Cannot borrow client for ssl://172.17.0.1:9711.
	at org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:145) ~[org.wso2.carbon.data

Maybe we need better naming for our definitions :) Or ideally find the ones that are already used for the same definitions.

Need a documentation site - the README is large and still falling behind the existing functionality.

Requirements:

• Must be generated from md or mdx
• Hosted in this repo

Look at docz:

• https://github.com/doczjs/docz
• https://github.com/rakannimer/create-docz-app#readme
• Example: http://welcome-ui.com/
• More examples: https://github.com/doczjs/docz/tree/master/examples

Hi, it's a little unclear what the contribution guidelines for the repo are. Are assigned Issues off-limits? Are can they still be worked on? Any commit message convention? Thank you!