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

DM-42404: Run Felis validation on schemas #180

Merged
merged 9 commits into from Jan 18, 2024
Merged

Conversation

JeremyMcCormick
Copy link
Collaborator

@JeremyMcCormick JeremyMcCormick commented Jan 11, 2024

This runs the new felis validate command on all SDM schemas in the ./yml dir. The felislint.yaml workflow was removed and replaced by validate.yaml. Other workflows were also updated to be compatible with the current version of Felis.

For now, Felis is installed via a github URL, as we are trying to reclaim the name from a dead package on PyPI. This can be changed to pip install felis when that is working properly.

This workflow validates all of the schemas in the ./yml directory using
the "felis validate" command. For now, Felis is installed using a
github URL. This can be changed to "pip install felis" once the package
is available on PyPI.
Install Felis rather than using a separate requirements.txt file, as
this may contain conflicting depedency versions.
Run the validation on all updates to the repository, which will also
automatically run as a PR check.
This should be helpful for developers as they incrementally commit
changes on branches. It will also run automatically as a check on PRs.
Copy link
Contributor

@cbanek cbanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't you want to delete felislint.yaml?

Anyway, this all looks reasonable, but I do see there's a fail to run on the felislinter.yaml action?

.github/workflows/yamllint.yaml Outdated Show resolved Hide resolved
.github/workflows/validate.yaml Show resolved Hide resolved
@JeremyMcCormick
Copy link
Collaborator Author

Don't you want to delete felislint.yaml?

Anyway, this all looks reasonable, but I do see there's a fail to run on the felislinter.yaml action?

I deleted this and made note of a few warnings which are not replicated by the Pydantic model.

https://jira.lsstcorp.org/browse/DM-42482

This workflow is superseded by validation using the Pydantic data
model.

There were a few warnings from checks not implemented with the new
validation, and these have been noted in Jira:

https://jira.lsstcorp.org/browse/DM-42482

These can be added to the new validation framework if necessary.
This was only called from a single Github workflow and should be
unnecessary now that validation has been implemented in Pydantic.
@JeremyMcCormick JeremyMcCormick merged commit 8ac3a39 into main Jan 18, 2024
4 checks passed
@JeremyMcCormick JeremyMcCormick deleted the tickets/DM-42404 branch January 18, 2024 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants