Pin bertron-schema version to v0.1.0-alpha.10 using Git tag

[shreddd]

I'd like to switch to using the tagged version of the schema.

As a one time fix I would also like to update the tag "v0.1.0-alpha.10" on this repo to match this commit.

I realize that this is essentially re-tagging things, but it will allow us to bring all the repos in sync

[eecavanna]

As a one time fix I would also like to update the tag "v0.1.0-alpha.10" on this repo to match this commit.

I'd rather not redefine an existing Git tag in this repo, since this repo has a GHA workflow that has already used the tagged commit to build a container image (whose image tag is derived from the Git tag). I'd prefer creating a new tag; e.g. v0.1.0-alpha.11. I'm OK with there being multiple tags pointing to the same commit (which would be the case in the other repos).

[eecavanna]

LGTM with one exception:

There is one more place where the schema hash is used. It's the default value of one of the CLI options in the ingester.

bertron/mongodb/ingest_data.py

Line 201 in 0a2c92d

default="https://raw.githubusercontent.com/ber-data/bertron-schema/82498f5f5cbc71ed7abf71b8e2c01d15c003f8d8/src/schema/jsonschema/bertron_schema.json",

Once that's been updated, I'm OK with this being merged in.

[shreddd]

LGTM with one exception:

There is one more place where the schema hash is used. It's the default value of one of the CLI options in the ingester.

bertron/mongodb/ingest_data.py

Line 201 in 0a2c92d

default="https://raw.githubusercontent.com/ber-data/bertron-schema/82498f5f5cbc71ed7abf71b8e2c01d15c003f8d8/src/schema/jsonschema/bertron_schema.json",

Once that's been updated, I'm OK with this being merged in.

I agree

[eecavanna]

Sorry, I don't think I used the right syntax. Will fix and commit again.

[eecavanna]

Yeah, I left off the /src/schema/jsonschema/bertron_schema.json (oops)