Skip to content

feat: As a user i want to configure sensitive limit-count plugin properties using environment variables #10597

Description

@ikatlinsky

Description

Description

limit-count plugin has several sensitive properties (contain passwords and username) or fields which should be the same for all instances of plugins in side apisix server, for example:

  • redis_username
  • redis_password
  • redis_host
  • redis_port
  • redis_cluster_nodes
  • redis_cluster_name

Use case

We have a single Redis cluster which should be used for all limit-count plugins we do not want to duplicate Redis-related settings and we do not want to include redis_password directly in configuration scripts which create plugins inside routes.

Proposal

Make all string and string array properties support environment variables.

If the property is an environment variable it should be prefixed with env: or $env:. In other cases, properties will be treated as a plain value.

Metadata

Metadata

Assignees

Type

No type

Projects

Status
✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions