hashicorp / hashicorp/consul-template

After running the consult for a period of time, the consult ui and key/value data are gone, leaving an unknown empty folder

Open
#1,771 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
4.8k
Forks
801
Avg merge
4h 5m
Merged PRs (30d)
6

Description

Please note that the Consul Template issue tracker is reserved
for bug reports and enhancements. For general usage questions,
please use the Consul Community Portal or the Consul mailing list:

https://discuss.hashicorp.com/c/consul
https://groups.google.com/forum/#!forum/consul-tool

Please try to simplify the issue as much as possible and include all the
details to replicate it. The shorter and simpler the bug is to reproduce the
quicker it can be addressed. Thanks.

### Consul Template version

Run `consul-template -v` to show the version. If you are not
running the latest version, please upgrade before submitting an
issue.

### Configuration

```hcl
# Copy-paste your configuration files here. Only include what is necessary or
# what you've changed from defaults. Include all referenced configurations.

```

```liquid
# Copy-paste your Consul Template template here
```

```liquid
# Include sample data you reference in the template from Consul or Vault here.
```

### Command

```shell
# Place your Consul Template command here
```

### Debug output

Provide a link to a GitHub Gist containing the complete debug
output by running with `-log-level=trace`.

### Expected behavior

What should have happened?

### Actual behavior

What actually happened?

### Steps to reproduce

1.
2.
3.

### References

Are there any other GitHub issues (open or closed) that should
be linked here? For example:
- GH-1234
- ...

Contributor guide

Open the contributing guide

Research direction

The report does not include a Consul Template version, configuration, template, command, debug output, or reproduction steps. Start by gathering those details, including trace output from the consul-template command; done means reproducing the missing UI and key/value data and documenting the expected and actual behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.