英雄招募

成为 Doocs 项目维护者

本项目 advanced-java，包括 Doocs 开源组织下的所有项目，都欢迎各位朋友参与完善。

如果你提交的内容有价值，且具备规范性，将有机会提升为项目的维护者，直接参与项目的 review、merge 等维护工作，提交内容时也可以直接 push 到 doocs/advanced-java 主分支 master 下，无须提交 PR 等待 review。

目前 advanced-java 只有 [yanglbme](http

See nats-io/nats-server#944. I spent a couple of hours debugging this issue and believe that it probably should be documented in README (if I've understood things correctly).

Expected Behavior / New Feature

As stated in the ReadMe, Ocelot depends on .net standard 2.0 and should be usable with full .net framework

Actual Behavior / Motivation for New Feature

Nuget states that Ocelot 14.0.9 depends on .net core 3.1

I'm running through the NGS tutorial, but couldn't find the NGS URL. I tried looking in this repo, but didn't see any mention of it. I eventually did find it, but then I started wondering...

Should we mention the URL somewhere here? Maybe even have a variable for it, like nats.DefaultURL, but instead nats.NGS.

That way we get:

nats.Connect(nats.NGS, nats.UserCredentials("user.cre

执行流水线时，对于用户看到是键值(可理解的描述)
但对于编辑者，则能拿能对应的value，可以是整数也可以是字符串。或者全是字符串，这样通用些。

参数配置时填写：
【全停全启】--> restart_all
【重新加载】--> reload_all
【仅解压】 --> unpack
例如：用户看到上面三个选项，用户选择 【全停全启】时，则拿到 其对应的值: “restart_all ”

Now that the core foundation to resolve metadata properties as native labels from the container images, we would have to think about how to promote this as a pattern in SCDF for K8s users.

Notes:

1. Everyone relies on a private Docker registry for production deployments
2. The default being DockerHub, and the procedure for external/private Docker registry configuration needs to be documented

it seems older versions of Nginx could be cutting public ingress endpoints. Prescribe from deployment steps 1.24.7 tested version or higher to avoid this issue.

related: #144

Currently, users can't see all the short links they created.

Add GraphQL API to show all the linked created by the user after he, she or they signed in.

We are recommending validating resources by hand: https://preliminary.istio.io/docs/ops/common-problems/validation/#seemingly-valid-configuration-is-rejected

We should mention istioctl analyze or validate or whatever the latest tool is

I'm curious as to what the recommended approach is on testing operations? We've started using them and it's a good concept, but I'm uncertain whether these are to be tested as unit or functional as I referred to the wiki on testing jobs and features.

Currently one of my operations relies on a DTO passed through to it that has been processed in previous jobs. If I was to functionally test it, I