configuration-management
Here are 1,283 public repositories matching this topic...
Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new autostart option to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?
Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.
-
Updated
Nov 21, 2021 - Java
-
Updated
Nov 19, 2021 - Python
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??
-
Updated
Nov 19, 2021 - Rust
-
Updated
Nov 18, 2021 - Python
-
Updated
Oct 20, 2021 - JavaScript
-
Updated
Jul 5, 2021 - C++
-
Updated
Oct 20, 2021 - Ruby
-
Updated
Nov 16, 2021 - Python
-
Updated
Nov 11, 2021 - Java
-
Updated
Nov 16, 2021 - Python
-
Updated
Nov 4, 2021 - Python
-
Updated
Nov 21, 2021 - Rust
-
Updated
Jul 6, 2021 - C
Similar to the Email validator.
We are adding support custom resource ordering in kpt live with the introduction of the depends-on annotation (GoogleContainerTools/kpt#2565). The resource references includes the namespace and name of resources, which means we should make sure they are updated when using the set-namespace and ensure-name-substring functions are used. We should update the functions to
-
Updated
Dec 15, 2020 - Python
-
Updated
Nov 21, 2021 - TypeScript
-
Updated
Oct 1, 2021 - C#
-
Updated
Nov 21, 2021 - C#
-
Updated
Feb 5, 2019 - Python
-
Updated
Nov 12, 2021 - Python
-
Updated
Nov 17, 2021 - Go
-
Updated
Jul 1, 2020 - Java
-
Updated
Nov 11, 2021 - Shell
-
Updated
Nov 19, 2021 - Ruby
-
Updated
Aug 24, 2021 - Java
Improve this page
Add a description, image, and links to the configuration-management topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the configuration-management topic, visit your repo's landing page and select "manage topics."



The code coverage https://codecov.io/github/ctripcorp/apollo seems to be less than 60%.
It would be great if it can be brought up around 80-90%.