Decommissioning Satellite sites

How to decommission a satellite site

1. To prevent access to the site, create a request in service-now to remove the DNS mapping ( both A record and CNAME record). Create a request to remove the redirection from satellitesite.com to www.satellitesite.com if any. This should be done on planned date of decommission.

2. Take backup of the dataset, from Sanity datastore and archive it.

3. Stop and delete the web and studio applications from radix.

4. Code clean up for the dataset

   1. Remove the language configuration for the dataset in the file satellitesConfig.js**
   2. Remove the dataset name from the file satellites.json from repository root.
   3. Remove all mentions of the satellite site domain in the repo, like in robots.txt

5. Remove the google tag manager container for the satellite site.

6. Remove the radix configuration for the satellite site from the radixconfig.yaml file both for web and studio, so the next deploy will not include this satellite.

7. Remove the feature flags for the dataset (if any) from FeatureFlags.js

8. Go to manage.sanity.io and disable CORS in the API tab to the satellite studio

   • Satellite studio url can be found in radix, or https://studio-[insertTheDatasetNameHere]-equinor-web-sites-[dev|preprod|prod].c2.radix.equinor.com/

9. Cookiebot configuration

   • Log in to the Cookiebot console, under Domains tab, delete the new satellite site url.
   • Remove the translation text for that satellite site (do not remove if the translation is being used by another site).

10. Add roles

    • Remove roles to Sanity.io
    • Remove roles to Microsoft Azure
    • Remove the Azure AD group for the satellite site.

11. Remove allowed-origins for fotoware function app

    • Remove the studio url in the allowed CORS origins to the bicep file in the internal repo and deploy azure setup to effect this change.

12. Delete the dataset from the project in sanity.io.