configuration-management

• I have checked the discussions
• I have searched the [issues](https://gi

Both versions of nacos2.0.0 and nacos2.0.2 were tried, unable to cluster successfully under mac and centos, the log output service is being restarted, unable to start normally, and cannot complete the election.
尝试了nacos2.0.0和nacos2.0.2两个版本，在mac和centos下都无法集群成功，日志一直输出服务在重启，无法正常启动，也无法完成选举.

Description

let's say I have an apache process group I want to control.

• when using supervisord.running, the name must be apache:* (which is the same notation used by supervisor)
• when using supervisord.dead, the name must be apache: (without the *)

As both states mirror each other, I expect them to use the same convention for name, the one from running since it

Basically we're in the DAG, so make sure we've let all the other resources (like files) get built (that might be used for the file server) before the server sends anything out. We could either block or just not return anything yet.

As an aside, does the rf.ReadFrom bit not get cancelled properly on close??

Hi,
thank you for the library. It really improved the way I approach configuration files.
Finally I have types and proper sections.
What I am missing is schema: I would love to be able to enforce that some parameters are obligatory, their type and provide a description, also raise an exception if there is some unknown parameter is configured.
I think I could use something like marshmallow

Similar to the Email validator.

Expected behavior

Formatting configs would not break yaml docs that includes anchors and references.

Actual behavior

Running the kpt fn render command on a configuration that includes anchors and references ends up putting the anchors before the references in the yaml, thereby making the yaml invalid.

Information

Steps to reproduce the behavior

kpt pkg get https: