-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for consul validate #518
Comments
Hello @Lusitaniae, Have you tried adding the main configuration file in the same command ? consul validate {{ consul_config_path }}/config.json {{ consul_configd_path }} I just opened a PR to add the configuration validation (cf #565). |
bastienwirtz
pushed a commit
to bastienwirtz/ansible-consul
that referenced
this issue
Feb 22, 2024
bastienwirtz
pushed a commit
to bastienwirtz/ansible-consul
that referenced
this issue
Feb 22, 2024
isakrubin
added a commit
to car-info/ansible-consul
that referenced
this issue
Jun 10, 2024
* upstream/master: Remove deprecated molecule/centos-stream-8 Fix rolling restart by waiting for consul leave and after restart Update molecule.yml --- (ansible-collections#597) Bump idna from 3.3 to 3.7 in the pip group across 1 directory (ansible-collections#596) Fix CI badge in README (ansible-collections#595) Fix ubuntu 22.04 molecule test to actually run on 22.04 (ansible-collections#594) feat: Configuration validation. fix ansible-collections#518 (ansible-collections#592) Fix error when creating gossip key (ansible-collections#558) adding become to service restarts (ansible-collections#571) Bump the pip group across 1 directories with 1 update (ansible-collections#590)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ideally we'd have some validation task when updating template files
I'm trying something like this
# validate: "consul validate %s {{ consul_configd_path }}"
Which fails with:
Related to hashicorp/consul#3897?
The text was updated successfully, but these errors were encountered: