Skip to content

Conversation

@gcoxmoz
Copy link
Contributor

@gcoxmoz gcoxmoz commented Nov 8, 2025

Notes: these are low-value domains that are configured in Markmonitor's 'forwarding dns' zones. I plan to pivot it all to refractr after this lands. We're well into "short-term breakage is okay" and I assume the liability therein.

Refractr PR Checklist

JIRA ticket: SREIN-636

When creating a PR for Refractr, confirm you've done the following steps for a smooth CI and CD experience:

  • Have you updated the relevant YAML in the PR?
  • Have you checked the relevant YAML for any possible dupes regarding your domain?
  • Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at refractr, is a temporary TLS 'outage' while waiting for certification via HTTP challenge okay? If not, add a note to the JIRA ticket.
  • If desired, have you generated the nginx config manually to confirm updates work as expected?

After PR merge, next steps include:

  • A merge to the main branch will automatically deploy refractr's stage environment -- deploying the prod environment requires a GitHub release to be created.
  • Once deployed, refractr's certmap must be updated and DNS entries must be changed -- SRE can help with this. Please pull someone in on the JIRA ticket or ask for help in #sre on Slack.

@gcoxmoz gcoxmoz requested a review from a team as a code owner November 8, 2025 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant