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

Put 'directory' attribute back into schema #3667

Closed
wants to merge 0 commits into from

Conversation

davedittrich
Copy link
Contributor

PR #3638 removed a central part of the schema that broke pytest-testinfra. I am assuming that a test for this was also removed, hence the unnoticed regression. I spent a little time looking into it and it looked like the schema validation is more a "does it parse" than "does it support all possible attributes."

@davedittrich davedittrich requested review from a team as code owners September 24, 2022 05:09
@davedittrich davedittrich requested review from Shaps, apatard, ganeshrn, priyamsahoo and shatakshiiii and removed request for a team September 24, 2022 05:09
@github-actions github-actions bot added the bug label Sep 24, 2022
@davedittrich
Copy link
Contributor Author

Actually, it does look like a unit test was also broken: src/molecule/test/unit/model/v2/test_verifier_section.py

https://github.com/ansible-community/molecule/pull/3638/files

I do not know how to run unit tests to verify that simply putting the "directory" attribute back in will work, but it looks like this should be done as well.

This was referenced Sep 24, 2022
@jsf9k
Copy link
Contributor

jsf9k commented Oct 17, 2022

I am hitting this issue as well, for example here. More generally, this issue is breaking all of our Ansible role builds that use a non-default location for the Molecule testinfra test code.

@jsf9k
Copy link
Contributor

jsf9k commented Oct 17, 2022

Resolves #3686

@ssbarnea
Copy link
Member

@jsf9k You forgot to rebase it

@jsf9k
Copy link
Contributor

jsf9k commented Oct 17, 2022

@jsf9k You forgot to rebase it

@ssbarnea - The PR was created by @davedittrich, not me.

@davedittrich - Can you rebase the PR? I doubt I have permissions to do that.

@jsf9k
Copy link
Contributor

jsf9k commented Oct 18, 2022

@davedittrich - Can you rebase the PR? I doubt I have permissions to do that.

I was able to successfully rebase locally (there were no conflicts), but as expected I lack the necessary permissions to force push to @davedittrich's branch.

@davedittrich
Copy link
Contributor Author

@jsf9k There you go! Thanks!

@davedittrich davedittrich deleted the fix-schema branch October 18, 2022 17:51
@jsf9k jsf9k mentioned this pull request Oct 18, 2022
@jsf9k
Copy link
Contributor

jsf9k commented Oct 18, 2022

@davedittrich closed this PR, so I assume his intent is that I create a new one from the rebased branch. I did just that in PR #3687.

@davedittrich
Copy link
Contributor Author

@jsf9k Sorry about that. My mistake. I thought everything was complete and misread the GitHub suggestions about being able to delete the branch. I'm glad you moved forward as you did. Thanks!

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.

None yet

3 participants