teler-waf is a Go HTTP middleware that protects local web services from OWASP Top 10 threats, known vulnerabilities, malicious actors, botnets, unwanted crawlers, and brute force attacks.
The current codebase has become too complex, and maintaining the dsl package within it has become increasingly difficult. Migrating the dsl package into its own repository will help in better organization, management, and versioning of this specific functionality. It will also facilitate easier collaboration and contribution from external parties who may only be interested in the DSL aspect.
Design
The dsl package will be extracted from the existing codebase and placed into its own repository. This will involve creating a new repository dedicated to the dsl (done at https://github.com/teler-sh/dsl) package and transferring all relevant code, documentation, and tests into it. The package will then be published as a standalone module, allowing it to be independently versioned and distributed.
Drawbacks
Increased complexity in managing multiple repositories.
Potential fragmentation of documentation and contribution efforts.
Additional overhead in maintaining separate versions for the dsl package.
Alternative Approaches
An alternative approach would be to refactor the existing codebase to simplify the dsl package within it. However, given the current complexity of the codebase, this may not be a feasible solution and could lead to further complications.
Unresolved Questions
What parts of the design are still undecided? Are there any outstanding questions or concerns that need to be addressed? For instance:
Summary
The
dslpackage will be removed from the codebase and migrated into a new repository, https://github.com/teler-sh/dsl.Motivation
The current codebase has become too complex, and maintaining the
dslpackage within it has become increasingly difficult. Migrating thedslpackage into its own repository will help in better organization, management, and versioning of this specific functionality. It will also facilitate easier collaboration and contribution from external parties who may only be interested in the DSL aspect.Design
The
dslpackage will be extracted from the existing codebase and placed into its own repository. This will involve creating a new repository dedicated to thedsl(done at https://github.com/teler-sh/dsl) package and transferring all relevant code, documentation, and tests into it. The package will then be published as a standalone module, allowing it to be independently versioned and distributed.Drawbacks
dslpackage.Alternative Approaches
An alternative approach would be to refactor the existing codebase to simplify the
dslpackage within it. However, given the current complexity of the codebase, this may not be a feasible solution and could lead to further complications.Unresolved Questions
What parts of the design are still undecided? Are there any outstanding questions or concerns that need to be addressed? For instance: