It might be optimistic to say that rolling over to a new key is 'at most a dozen clicks'. Hardcoded keys are a big one. But even just hunting down all config w

It might be optimistic to say that rolling over to a new key is 'at most a dozen clicks'. Hardcoded keys are a big one. But even just hunting down all config where the key needs to change can be a major hassle. Is there some ci yaml that expects a runner to have the key in a .env file that only runs on major release? Good chance you won't realize that key exists. Still a great idea to revoke those keys. But it will damage some customers in the short term. And they will be angry, as people often are when you demonstrate their mistake.