Skip to content
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.

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

Require at least one known subfolder for roles #3303

Merged
merged 1 commit into from
Apr 19, 2023
Merged

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Apr 18, 2023

Identified folders as roles only if they contain one of the known subfolders used by roles, such "tasks", "meta", "vars", "defaults", "handlers".

This behaviour change should prevent undesired identification of other folders as roles, like we seen on debops repository, where documentation folders were wrongly identified as roles.

@ssbarnea ssbarnea requested a review from a team as a code owner April 18, 2023 13:36
@ssbarnea ssbarnea requested review from a team, audgirka, shatakshiiii and Ruchip16 April 18, 2023 13:36
Identified folders as roles only if they contain one of the known
subfolders used by roles, such "tasks", "meta", "vars", "defaults",
"handlers".
@ssbarnea
Copy link
Member Author

Please note that "eco" pipeline failure seems expected in this case, as it does change the output for debops repository.

@ssbarnea ssbarnea merged commit fd23b3a into main Apr 19, 2023
@ssbarnea ssbarnea deleted the feat/role-subfolder branch April 19, 2023 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants