8000 Include blueprint input in automation trace by emontnemery · Pull Request #48575 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Include blueprint input in automation trace #48575

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Apr 1, 2021
Merged

Include blueprint input in automation trace #48575

merged 1 commit into from
Apr 1, 2021

Conversation

emontnemery
Copy link
Contributor

Proposed change

Include automation config before blueprint substitution in automation trace.

The automation's config before blueprint substitution is available in key blueprint_inputs in the trace.

Example:

Automation config:

id: sun
use_blueprint:
  path: test_event_service.yaml
  input:
    trigger_event: blueprint_event
    service_to_call: test.automation

Blueprint:

blueprint:
  name: "Call service based on event"
  domain: automation
  input:
    trigger_event:
    service_to_call:
trigger:
  platform: event
  event_type: !input trigger_event
action:
  service: !input service_to_call
  entity_id: light.kitchen

trace["blueprint_input"]:

id: sun
use_blueprint:
  path: test_event_service.yaml
  input:
    trigger_event: blueprint_event
    service_to_call: test.automation

trace["config"]:

id: sun
action:
  entity_id: light.kitchen
  service: test.automation
trigger:
  event_type: blueprint_event
  platform: event

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

@probot-home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with an integration (script) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@balloob balloob force-pushed the trace_blueprint_inputs branch from afbdb19 to eb28566 Compare April 1, 2021 18:38
@balloob balloob mentioned this pull request Apr 1, 2021
Merged
9 tasks
@balloob balloob merged commit 76d0f93 into home-assistant:dev Apr 1, 2021
@balloob balloob added this to the 2021.4.0 milestone Apr 1, 2021
balloob pushed a commit that referenced this pull request Apr 1, 2021
@emontnemery @balloob
Include blueprint input in automation trace (#48575)
231a55d
@emontnemery emontnemery mentioned this pull request Apr 2, 2021
Merged
27 tasks
@github-actions github-actions bot locked and limited conversation to collaborators Apr 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@balloob balloob balloob approved these changes

Assignees
No one assigned
Labels
cherry-picked cla-signed core has-tests integration: automation integration: script integration: trace new-feature small-pr PRs with less than 30 lines.
Projects
None yet
Milestone
2021.4.0
Development

Successfully merging this pull request may close these issues.
3 participants
@emontnemery @balloob @homeassistant
0