You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
The AFD infrastructure needs to be established as IaC to be replicated across multiple environments. This includes the provisioning of the AFD resource, the configuration of its Origin Groups, Routes, Rulesets and Custom Domains.
Suggested Solution
Tasks
Build the IaC workflow in development environment
Create a new SSW Repo - SSW.FrontDoor.IaC
Create two GitHub Environments - Staging and Production
Test IaC pipeline in Staging environment
Thanks!
The text was updated successfully, but these errors were encountered:
Bicep templates have been built and verified in Dev environment, however we cannot integrate them into staging/production until SysAdmins finish the staging AFD configuration to add the missing bits.
DONE:
AFD Resource
Origin Groups
Routes
Redirect rules
Missing:
Domain config (DNS zoning)
WAF policy config (missing basic WAF rules that should be there)
Once these are done, I can add them into the bicep template and we can integrate the IaC into staging.
The redirect rules have been added in my local dev branch, but have not been merged yet as we need to wait until the content review is complete before rolling these rules out.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Cc:
To Myself,
Pain
The AFD infrastructure needs to be established as IaC to be replicated across multiple environments. This includes the provisioning of the AFD resource, the configuration of its Origin Groups, Routes, Rulesets and Custom Domains.
Suggested Solution
Tasks
Thanks!
The text was updated successfully, but these errors were encountered: