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

Schema Enforcer Incorrectly Reports Location of Some Data Files #88

Open
PhillSimonds opened this issue Feb 11, 2021 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@PhillSimonds
Copy link
Contributor

Environment

  • Python version: 3.7.9
  • schema-enforcer version: 1.0.1

Expected Behavior

When schema-enforcer validate --show-checks is run and a data file exists at the base path in which schema enforcer is run, I expected schema enforcer to output the data file being evaluated as ./<file>

Observed Behavior

schema-enforcer validate --show-checks shows the data file being evaluated as .//<file>.

schema-enforcer validate --show-checks                                                        
Structured Data File                               Schema ID
--------------------------------------------------------------------------------
.//dns.yml                                         ['schemas/dns_servers']
./chi-beijing-rt1/syslog.yml                       ['schemas/syslog_servers']
./eng-london-rt1/dns.yml                           ['schemas/dns_servers']
./eng-london-rt1/ntp.yml                           ['schemas/ntp']

Steps to Reproduce

  1. Move the dns.yml file nested in schema enforcer's examples/example1/chi-beijing-rt1/ folder. to schema enforcer's examples/example1 folder (e.g. examples/example1/chi-beijing-rt1/dns.yml -> examples/example1/dns.yml
  2. Change directories into examples/example1
  3. Run schema enforcer and observe the output (denoted in the Observed Behavior section)
@PhillSimonds PhillSimonds self-assigned this Feb 11, 2021
@PhillSimonds PhillSimonds added the bug Something isn't working label Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant