[
https://issues.apache.org/jira/browse/FLINK-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608314#comment-15608314
]
ASF GitHub Bot commented on FLINK-4876:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2680
I added a new way to define configuration options (see below). It is a much
more maintainable way of defining configuration options.
Would be great if we used that for all new options that we create, and
lazily migrate existing parameters to that pattern.
```java
ConfigOption<Double> threshold = ConfigOptions
.key("cpu.utilization.threshold")
.defaultValue(0.9).
.withDeprecatedKeys("cpu.threshold");
```
Here is a complete example:
https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/configuration/HighAvailabilityOptions.java
> Allow web interface to be bound to a specific ip/interface/inetHost
> -------------------------------------------------------------------
>
> Key: FLINK-4876
> URL: https://issues.apache.org/jira/browse/FLINK-4876
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.2.0, 1.1.2, 1.1.3
> Reporter: Bram Vogelaar
> Assignee: Bram Vogelaar
> Priority: Minor
>
> Currently the web interface automatically binds to all interfaces on 0.0.0.0.
> IMHO there are some use cases to only bind to a specific ipadress, (e.g.
> access through an authenticated proxy, not binding on the management or
> backup interface)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
