When a challenge service is deployed, it will sync the challenge automatically (to include connection_info) and also possibly make a previously hidden challenge (e.g. created with --hidden or just hidden in the admin panel manually) visible (because it does not define state in challenge.yml).
I think it's best to always leave the state as-is with the deployment because the sync happens automatically - the user might be unaware that the challenge he or she made hidden has now been made visible.
When a challenge service is deployed, it will sync the challenge automatically (to include connection_info) and also possibly make a previously hidden challenge (e.g. created with --hidden or just hidden in the admin panel manually) visible (because it does not define state in
challenge.yml).I think it's best to always leave the state as-is with the deployment because the sync happens automatically - the user might be unaware that the challenge he or she made hidden has now been made visible.