Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

removing_default_domains_refractr_stage #339

Merged
merged 1 commit into from
Jul 22, 2024

Conversation

Basma1912
Copy link
Contributor

Refractr PR Checklist

JIRA ticket: [link to relevant JIRA or other system ticket]

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

  • 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 Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • If desired, have you generated the Nginx manually to confirm addition works as expected?
  • If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • Confirm you are ready and able to perform the requested DNS creation or change post-deploy?

Signed-off-by: Basma1912 <basad@mozilla.com>
@Basma1912 Basma1912 merged commit 7f98ab2 into main Jul 22, 2024
1 check passed
@Basma1912 Basma1912 deleted the removing_default_domains_refractr_stage branch July 22, 2024 13:37
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.

2 participants