We currently build the images using inv and then we copy the binaries inside the container with a COPY instruction.
It'd be better to have the build process as part of the dockerfile itself. That will allow us to get rid of inv when publishing images and delegate everything to GH actions (which can be a follow up of metallb/metallb#1374 )
Is your feature request related to a problem? Please describe.
This is the logic currently implemented in the main branch:
If headers criteria are configured, a request is filtered in if it matches both headers and urls. If headers criteria are NOT configured, the probability options are used.
Some applications are not case-sensitive on the URL parameters, and may look for arguments presented under any fantasist format. One could argue that we could turn the complete string to lower case before performing the lookup, but that would also change the values, which is not desired. A better approach would be to improve url_param, urlp, and urlp_val() to take a
In the case of using openelb as the Kubernetes load balancing implementation, the allocation of openelb external-ip-pool can only be viewed on the terminal interface by accessing Kubernetes resources with kubectl. However, more and more kubernetes users are using specific dashboards to operate and manage clusters or workloads, such as KubeSphere. Therefore, the current usage is n
kind/feature
Categorizes issue or PR as related to a new feature.
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Can we force the new sanitizing key to be applied to the configuration on /refresh call?
Environment (please complete the following information):
.NET Core 3.1.3
Steeltoe Version 3.0.2
Additional context or links
I tried to work with Steeltoe's /env and /refresh endpoints. What I noticed is that the sanitizer works only when a project is started. When you add a k
Sometimes an upstream may return an error with HTML. For example public upstreams.
Right now Dshakle produces the following log:
WARN | ResponseParser | Failed to parse JSON from upstream: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
at [Source: (byte[])"
<!DOCTYPE html PUBLIC "-//W
Description
Reference