microservices
Here are 3,891 public repositories matching this topic...
Looks closely related to #779
I'm submitting a...
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
Middleware is being called for every endpoint a request route could potentially match.
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
Currently at 66.1%.
项目启动报WARN
日志
2019-06-12 12:04:59.670|/|WARN |main|o.s.b.c.p.PropertySourcesDeducer|Multiple PropertySourcesPlaceholderConfigurer beans registered [propertySourcesPlaceholderConfigurer, org.springframework.context.support.PropertySourcesPlaceholderConfigurer], falling back to Environment
Apollo Client => ConfigPropertySourcesProcessor
 tried: failed to req API:minion-register:8848/nacos/v1/ns/instance/beat. code:400 msg: java.lang.IllegalArgumentException: dom name can only have these characters: 0-9a-zA-Z-._:, current: DEFAULT_GROU
Hello,
I found recently that grpc-go was working on an xds implementation for service discovery, which is great.
Using current HEAD, I tried to get both resolver and balancer working. I managed to get something more or less working for resolver by reversing code & tests code on Gist but as for balancer, I didn't.
I unders
-
Updated
Jun 18, 2020
Copied from briandealwis/cram#5: @student-06 asked
It would be great if we can supply auth creds for registry using parameters since it removes the dependency on credential helpers.
My exact use case is: We are setting up a CI system for UI projects, where we need to push docker images (without daemon) to a local registry which has auth.
-
Updated
Jun 12, 2020
i find the root cause of this issue
see config/Docker.file
HEALTHCHECK --interval=10s --timeout=3s CMD curl -f http://localhost:8888/actuator/health || exit 1
values of 10s for interval and 3s for connect timeout is both too small, when the docker machine have a bit lo
Hello,
We're using etcdv3 with a self-signed cert. so we can't use the default micro binary although etcdv3 support has been built in since v1.11.0
Is there any approach to access it without rebuilding the micro binary?
If the rebuild is needed, where should I put the "tls.Config initialize" code?
micro version: 1.11.0
Thanks.
refer, #210 #178
update:
It seems mi
Currently, we ask contributors to strive for consistency with existing code, but it would be helpful to clarify the following regarding docstrings:
- Docstrings should begin with a short (~70 characters or less) summary line that ends in a period.
- The summary line should begin immediately after the opening quotes (do not add a line break before the summary line)
- The summary line should de
Prerequisites
- I am running the latest version. (
up upgrade
) - I searched to see if the issue already exists.
- I inspected the verbose debug output with the
-v, --verbose
flag. - Are you an Up Pro subscriber?
Description
It would be great to add regex capabilities to redirects like so:
redirects: {
"/folder/:slug(regexhere)": {
"location": "https
The Go documentation states the following on http.Request.RemoteAddr
:
The HTTP server in this package sets RemoteAddr to an "IP:port" address before invoking a handler.
Therefore, you could expect that a code like this is correct:
package main
import (
"fmt"
"net"
"net/http"
"github.com/go-chi/chi"
"github.com/go-chi/chi/middleware"
)
func main() {
r
[E2E] Fix Makefile to allow 'make test-e2e-all' to work on Windows + Minikube + MinGW + GitBash
Current behavior
Issue: Windows + minikube + MinGW + GitBash + make (gets stuck)
asouza@ASOUZA-DESKTOP MINGW64 /c/Code/dapr/dapr (master)
$ make test-e2e-all
DAPR_TEST_NAMESPACE=dapr-tests DAPR_TEST_TAG=dev DAPR_TEST_REGISTRY=docker.io/artursouza DAPR_TEST_MINIKUBE_IP= go test -v -tags=e2e ./tests/e2e/...
Workaround: see how I had to manually run the same command but set t
Keep the number of the dependencies maven artifacts to the minimum required and document clearly their usage
At the moment we have in Activiti:
- activiti-dependencies
- [activiti-api-dependencies](https://github.com/Activiti/Activiti/blob/develop/activiti-api/activiti-
-
Updated
Jun 15, 2020 - JavaScript
Bug report
General Information
- Cilium version: 1.7.2
- Kernel version: 5.6.6
- Orchestration system version: Kubernetes 1.18.2
I'm using terraform to spool and deploy kubeadm on AWS.
How to reproduce the issue
The issues is that if the Cloud Controller Manager is not brought up before Cilium the node is brought, and the operator starts running ENIs will be attached t
What happens?
官方例子,修改react16即create-react-app项目后,主项目报错You need to export the functional lifecycles in react16 entry
Mini Showcase Repository(REQUIRED)
https://github.com/umijs/qiankun/tree/master/examples
How To Reproduce
Steps to reproduce the behavior: 1. 2.
Expected behavior 1. 2.
Context
- qiankun Version:
- Platform Version:
- **Browser Ve
**Do you want to request a feature or report a bug?
Feature?
What is the current behavior?
Session object ACLs require both the key and the api_id field of the ACL definition to match.
If they mismatch the API does not throw an error.
What is the expected behavior?
The Gateway API should report the discrepancy to stop the token from being generated.
-
Updated
Jun 23, 2020 - Go
As part of clarifying what is part of the open source offering and what is examples or private code, we should signal these differences using package names/namespaces.
Suggested solution:
- Let all public, published packages retain their
@backstage
namespace. - Change all private packages in the open source project (
plugins/home-page
,plugins/welcome
) to be under an@internal
names
-
Updated
Jul 18, 2019
Improve this page
Add a description, image, and links to the microservices topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the microservices topic, visit your repo's landing page and select "manage topics."
Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.
You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.
At first, we want to collect ideas for best practices, solidify a list