Pantheon hosting is in its second day of having issues. I cannot access my dashboard. Curious if anyone has any insight into this.

TLDR;

Since I work on 3 Drupal environments (local, staging, prod) and each has a DB, every time I add a new block locally, then deploy to staging, it disappears. Of course, different DBs, different UUIDs, I get why this is happening. The block I have locally simply doesn't exist on staging, I need to go there and create it, add to the block layout, dump DB and do a config export from this DB, commit to the codebase and deploy again. Same with prod.

So around 10 steps and 4 deployments for adding a block to a Drupal website. How do you solve it? Simply ignoring block configs has obvious downsides.

More details

I add a new promo banner block locally → commit config → deploy to staging → block is gone because the UUID is different on staging. I then have to dump staging DB, re-export, merge the diff, redeploy. Then repeat the whole thing for prod. For a single block.

I know I could just throw `block.block.*` into config_ignore and call it a day, but that feels stupid - no git history, no rollback, one wrong click from me or teammates and the layout is broken on prod with no way to trace what happened.

My semi-idea

Ignore only the blocks that actually cause problems (views blocks, custom content blocks) but keep tracking structural ones like menus and branding.

Is this roughly what others do? Is there a cleaner solution I'm missing? Would love to hear how teams with a lot of blocks are handling this.