add 1st draft for charm architecture docs#534
Merged
Conversation
erinecon
reviewed
Jun 4, 2026
erinecon
left a comment
Contributor
There was a problem hiding this comment.
Thanks so much for drafting this Explanation page 🎉 some initial thoughts from me
erinecon
reviewed
Jun 8, 2026
erinecon
left a comment
Contributor
There was a problem hiding this comment.
Thanks so much for adding more information to this page! This round of comments contains nits + questions about the ddos-configurator
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
- Code-format charm names in README links - Rename section header to 'High-level overview of deployment' - Update Container_Boundary title to 'HAProxy deployment' - Fix ddos component ID conflict in C4 diagram - Add ddos-protection relation to diagram - Add UpdateRelStyle() calls for improved diagram readability - Expand SPOE and OIDC acronyms in full on first use - Add ddos-configurator description paragraph - Enhance integrations section with context and ddos-configurator link
erinecon
approved these changes
Jun 22, 2026
erinecon
left a comment
Contributor
There was a problem hiding this comment.
Thanks so much! Nits only on the charm naming. But nothing that's blocking :D
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
Co-authored-by: Erin Conley <erin.conley@canonical.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Add
project-architecture.mdto document the overall architecture of the haproxy monorepoChecklist
docs/changelog.mdwith user-relevant changesdocs/release-notes/artifacts. If no change artifact is necessary, I tagged the PR with the labelno-release-note.(e.g., in
.github/workflows/integration_tests.yaml, ensure themoduleslist is correct)terraform fmtpasses andtflintreports no errors