Skip to content

Possible duplicate registry definitions in main.yaml at line 78 #2673

Description

@GiovanniCapizzi

Hi,
while reviewing the file main.yaml, I noticed that line 78 seems to define multiple register at the same parent level.

Image

Could this be a mistake or an unintended duplication?
If so, would the correct approach be to use a single register key?

Without this change it gives:

fatal: [localhost]: FAILED! => {"msg": "The conditional check 'component_data.resources|length > 0' failed. The error was: error while evaluating conditional (component_data.resources|length > 0): 'component_data' is undefined. 'component_data' is undefined"}

Thanks in advance for the clarification!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions