Add verify_ssl option for connection setup to synology_dsm#42539
Add verify_ssl option for connection setup to synology_dsm#42539Quentame merged 1 commit intohome-assistant:devfrom
Conversation
16430fc to
0435379
Compare
Quentame
left a comment
There was a problem hiding this comment.
LGMT, just a remark about translations.
| "password": "Contrasenya", | ||
| "port": "Port", | ||
| "ssl": "Utilitza un certificat SSL", | ||
| "username": "Nom d'usuari" |
There was a problem hiding this comment.
Does all translations files are updated with this command python3 -m script.translations develop ?
If no:
You should not change translations files (except english, with the right command https://developers.home-assistant.io/docs/internationalization/core#test-translations).
Translations are handled on lokalise.com by translator contributors and update by a "translation update" commit like 026e006
See the translation documentation : https://developers.home-assistant.io/docs/translations
There was a problem hiding this comment.
oh ok ... I did not know that. I have simply get the translation out of another intergration and copy&pasted them 😄
I will have a look into your mentioned approach and will update the PR properly
0435379 to
74fc9bf
Compare
|
current failing/flapping tests are fixed with #42614 therefore I rebased to newest |
74fc9bf to
dfad311
Compare
Quentame
left a comment
There was a problem hiding this comment.
Need to remove the de.json modifications.
Should be from the translation website.
dfad311 to
d6b7552
Compare
|
OK, now I get it 😃 One short question - when will the translation for DE (and all other available languages) be added, especialy when using common string relations: |
The will be added by the "update translation" commit, see #42539 (comment) For common string, that I am not an expert of, maybe #40578 can help 😊 |
|
Thanks 🎉 |
| vol.Optional(CONF_PORT): cv.port, | ||
| vol.Optional(CONF_SSL, default=DEFAULT_SSL): cv.boolean, | ||
| vol.Optional(CONF_SSL, default=DEFAULT_USE_SSL): cv.boolean, | ||
| vol.Optional(CONF_VERIFY_SSL, default=DEFAULT_VERIFY_SSL): cv.boolean, |
There was a problem hiding this comment.
Even though this integration does support the configuration flow, we still do not accept changes to the YAML configuration.
This PR, therefore, violates ADR-0010: https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision
There was a problem hiding this comment.
I think we should just remove the change to the config yaml schema. The rest is ok I think.
There was a problem hiding this comment.
Oh wait, we can drop yaml support 💁♂️
There was a problem hiding this comment.
Ok, I've seen that I'm on "Watch release" on the architecture repo, that explain things 😅
Do you think it's possible to make a release when a new ADR comes out ?
So it won't spam but let followers up to date.
There was a problem hiding this comment.
@Quentame Well... you have been notified of this 4 days ago as well:
See: #42539 (comment)
There was a problem hiding this comment.
Indeed 😞
Was too quick on reading apparently.
To forget me, let me remove YAML support.
|
This PR broke existing config entries |
Proposed change
This PR make use of new features in python-synology lib v1.0.0 and add the verify_ssl option for connection setup.
Documentation is updated with home-assistant/home-assistant.io#15413
This PR resolves also an "bonus issue" from #34888
Rebase will be done, when #42523 is merged
Type of change
Additional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: