Skip to content

Add some more information about our WAF set up to the documentation #602

@mikelittle

Description

@mikelittle

@rmccue shared a response to a customer from about our WAF configuration in Slack https://hmn.slack.com/archives/C01CD62UNDN/p1734011343668479

Though we cannot share all of the information for commercial/Confidentiality reasons, we can likely enhance the documentation we currently provide https://docs.altis-dxp.com/cloud/firewall/


Acceptance Criteria


For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to a milestone?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
    • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
  • Is there a roll-out (and roll-back) plan if required?

Metadata

Metadata

Assignees

Labels

could haveCould be done, or nice to have, low priority for nowdeveloper advocacyDeveloper Advocacy related tasks

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions