Integration Manifestation

balloob commented 5 years ago

In #22699 we have introduced manifests to all integrations. Now it's time to use them when manifests are available.

Manifest validator

[x] Script to validate that each integration has a manifest with the required fields and that fields are the correct types #22708

Codeowners

[x] Generate CODEOWNERS based on a core template + fetch from manifests #22705
[x] Mention code owners when label of integration that they own is added to an issue or PR

Requirements

[x] Generate requirements_* based on manifests #22718
[x] Remove REQUIREMENTS from all integrations. #23024
[ ] ~~Deprecate REQUIREMENTS for custom components~~
[x] Install requirements from manifest (fallback to current REQUIREMENTS) #22717

Dependencies

[x] Load dependencies from manifest (fallback to current DEPENDENCIES) #22716
[x] Remove DEPENDENCIES from all integrations. #23024
[ ] ~~Deprecate DEPENDENCIES for custom components~~
[x] Use manifest when determining circular dependencies #22908

Document update

[x] PR template #22751
[x] Dev doc update home-assistant/developers.home-assistant#214

rohankapoorcom commented 5 years ago

I'm working on

Load dependencies from manifest (fallback to current DEPENDENCIES) Install requirements from manifest (fallback to current REQUIREMENTS). Generate requirements_* based on manifests

cgtobi commented 5 years ago

What is missing here? DEPENDENCIES and REQUIREMENTS are removed from integrations if I didn't miss any.

MartinHjelmare commented 5 years ago

If it's possible, we should install integration requirements before validating the integration config so requirements are available in config validation.

balloob commented 5 years ago

I will add that to #23112

balloob commented 5 years ago

363b3c5 👍

frenck commented 5 years ago

I think this issue has been completed and can be closed @balloob ?

balloob commented 5 years ago

Yessssss 💃

home-assistant / core