hashicorp / boundary

Boundary enables identity-based access management for dynamic infrastructure.
https://boundaryproject.io
Other
3.83k stars 281 forks source link

illegal char in event filtering #4363

Closed yongzhang closed 7 months ago

yongzhang commented 7 months ago

Describe the bug Cannot start boundary because of illegal char in event filtering. Boundary version: 0.15.0

To Reproduce Steps to reproduce the behavior:

  1. Add below event sink:

      events {
        audit_enabled        = true
        observations_enabled = true
        sysevents_enabled    = true
        telemetry_enabled    = false
    
        sink "stderr" {
          name         = "all-events"
          description  = "All events sent to stderr"
          event_types  = ["*"]
          format       = "cloudevents-json"
          deny_filters = [
            '"/data/request_info/path" == "/health"'
          ]
        }
      }
  2. Start boundary service see error:

    Feb 06 04:47:28 ip-10-130-19-94 systemd[1]: Started "HashiCorp Boundary - Identity-based access management for dynamic infrastructure".
    Feb 06 04:47:28 ip-10-130-19-94 boundary[874]: Error parsing config: Error parsing KMS HCL: At 15:7: illegal char
    Feb 06 04:47:28 ip-10-130-19-94 systemd[1]: boundary.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
    Feb 06 04:47:28 ip-10-130-19-94 systemd[1]: boundary.service: Failed with result 'exit-code'.
    Feb 06 04:47:33 ip-10-130-19-94 systemd[1]: boundary.service: Scheduled restart job, restart counter is at 1.
    Feb 06 04:47:33 ip-10-130-19-94 systemd[1]: Stopped "HashiCorp Boundary - Identity-based access management for dynamic infrastructure".

image

I don't see any wrong chars here by checking the docs, please help, thanks. I also tried allow_filters config from here, it reports the same error.

Expected behavior A clear and concise description of what you expected to happen.

Additional context Add any other context about the problem here.

yongzhang commented 7 months ago

Ok, found the cause, submitted PR to fix docs: https://github.com/hashicorp/boundary/pull/4365