This covers the corner case where for some reason (e.g. invalid github key), updating secret fails.
With the current code, the old key will already be deleted and other workflows that use the secret will stop working.
With the proposed code, both the new and the old keys will still exist and other workflows will continue working. If the failure is not handled, the next rotation will also fail because it will have >1 keys.
This covers the corner case where for some reason (e.g. invalid github key), updating secret fails. With the current code, the old key will already be deleted and other workflows that use the secret will stop working. With the proposed code, both the new and the old keys will still exist and other workflows will continue working. If the failure is not handled, the next rotation will also fail because it will have >1 keys.