-
Trying to get a simple sample running for a playbook.
```
resource "ansible_playbook" "playbook" {
playbook = "./ansible/playbook.yml"
name = ansible_host.basic.name
#### ignor…
-
Some RPC calls might cause panic of the Ethermint RPC server. Here's a log.
Is there anything that we could do about it? The correct behavior should be to check the
signature length and return er…
-
### Is your feature request related to a problem? Please describe.
I'm setting up AWX to install FluentD on VMs (not in Containers). Ansible's "ansible.builtin.service" doesn't have command line argu…
-
CC @Jake-Moss
The idea of higher-level interfaces is discussed in gh-53. I would imagine that ultimately the usual way to create a multivariate polynomial would look something like:
```python
fr…
-
I named a positional argument `version` which resolved in very weird behaviors. After quite some debugging I realized that during parsing you convert positional arguments into options yet you don't ve…
AuHau updated
3 years ago
-
For failed arguments offer an option to correct them
- should required arguments be handled by this always?
- What about clients that don't have a console? Default to throw? Opt-in vs Opt-out feature?…
-
Each method parses the arguments independently. Code might be much simpler if we parsed the arguments once in omni.py and then passed a struct with the values filled in around. So all the string parsi…
-
There are multiple separate implementations of setting default values for config and reading them from file. Setting precedence is also a bit brittle based on how/where settings are loaded and command…
-
Currently, the semantic action are called whenever the sub-expression is parsed. It means that if the parsing fails upwards, the result of the semantic action will be dropped. This is terrible if the …
-
```
There are twoissues with current command-line parsing:
1. TPC silently ignores unknown options (users don't know that they made a
mistake)
2. TPC performs actions dictated by command-line argumen…