⚠️ Deployments - change from VM to Blob storage

SSWConsulting / SSW.People

This is the site generator for SSW.People. ▶️ Video: http://r.ssw.com/SSW-people

https://ssw.com.au/people

MIT License

12 stars 10 forks source link

⚠️ Deployments - change from VM to Blob storage #622

Closed wicksipedia closed 3 months ago

wicksipedia commented 6 months ago

Cc: @adamcogan

We need to decommission the VM we are deploying to and as a result switch to Azure Storage (blob storage)

### Tasks
- [x] Migrate builds/deployments from AzDO Pipelines to GitHub Actions?
- [x] Spin up Azure storage account and enable web server
- [x] Change deployments from IIS WebDeploy to AZ CLI file copy
- [x] Profiles - should trigger production
- [x] Change Cloudflare config to route `/people` to new storage account

More Information

Screenshots

Thanks!

wicksipedia commented 3 months ago

update on this issue - main now deploys to a new staging environment - https://sapeoplestagjthgmptzb46i.z8.web.core.windows.net/people

release/* branches will deploy to a new prod environment - https://sapeopleprod7bktxxg33i3v.z8.web.core.windows.net/people

I'd warn against creating a new prod release as there are some breaking changes:

redirects are page driven - change from IIS redirects to Gatsby api calls (generated pages with meta refresh redirects)
filters do NOT work on staging - they potentially need a rewrite
I'm noticing an odd console error r[@context] etc (even when developing locally)

wicksipedia commented 3 months ago

reopening - due to outstanding tasks

jernejk commented 3 months ago

Adding a few tasks for this.

Filters not working on staging

Tasks

[x] Investigate how filters are working
[x] Diagnose why filters break in staging but not locally
[x] Fix

jernejk commented 3 months ago

I have created a PR to push Profile changes to staging: https://github.com/SSWConsulting/SSW.People.Profiles/pull/1210

As per my conversation with @wicksipedia, it should be more consistent with SSW.Rules and using GH workflows instead of sh script. I initially tried to write YAML code but deleted it as it was too hard to verify it without permissions to run workflows. I'll ask SysAdmins to gain access.

NOTE: Fixed build issue that prevented CRM changes to get into production. https://github.com/SSWConsulting/SSW.People/issues/650

wicksipedia commented 3 months ago

The GitHub Action to trigger the build would look like https://github.com/SSWConsulting/SSW.Rules.Content/blob/main/.github/workflows/main-trigger-rules-deploy.yml

It uses app registration to get a token to do the workflow_dispatch

jernejk commented 3 months ago

✅ All done.