configuration-management
Here are 1,244 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
Aug 30, 2021 - Java
-
Updated
Aug 13, 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
Aug 30, 2021 - Rust
-
Updated
Aug 27, 2021 - Python
-
Updated
Jul 5, 2021 - C++
-
Updated
Jul 23, 2021 - JavaScript
-
Updated
Aug 8, 2021 - Ruby
-
Updated
Aug 19, 2021 - Java
-
Updated
Aug 18, 2021 - Python
-
Updated
Aug 24, 2021 - Python
-
Updated
Aug 25, 2021 - Python
-
Updated
Aug 23, 2021 - Rust
-
Updated
Jul 6, 2021 - C
Similar to the Email validator.
Describe your problem
When users run a mutator (e.g. set-annotations), the output doesn't tell them which files changed. The only way a user can figure out which files were affected is by looking through them manually or doing git status or however they might normally be notified of changes to files.
It would be nice if we were able to notify the user which files changed as a result
-
Updated
Dec 15, 2020 - Python
-
Updated
Aug 15, 2021 - TypeScript
-
Updated
Feb 5, 2019 - Python
-
Updated
Apr 12, 2021 - C#
-
Updated
Jul 1, 2020 - Java
-
Updated
Aug 29, 2021 - C#
-
Updated
Aug 28, 2021 - Ruby
-
Updated
Aug 25, 2021 - Python
-
Updated
Aug 25, 2021 - Shell
-
Updated
Aug 19, 2021 - Go
-
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%.