8000 Refactored and deployed event schema stack by victorskl · Pull Request #266 · umccr/orcabus · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Refactored and deployed event schema stack #266

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

Merged
merged 2 commits into from
May 3, 2024
Merged

Conversation

victorskl
Copy link
Member
  • Finalised SequenceRunStateChange event schema - trim & case
  • Relocated event schemas directory into docs
  • Deployed schema stack

Related #257

* Finalised SequenceRunStateChange event schema - trim & case
* Relocated event schemas directory into docs
* Deployed schema stack

Related #257
@victorskl
Copy link
Member Author

I will need to get merge this refactor PR first, before following up next for workflow event schema. At the same time, I need your input and review. So, will be waiting.

Copy link
Member
@williamputraintan williamputraintan left a comment

Choose a reason for hiding this comment

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

Hmmm, I just have the preference of having as close as possible to the code so perhaps stay as it is in the config folder 😅 (or maybe at the stack folder) ? I think the docs/ should be just a bunch of explanation on how to do what instead of relying some actual content.

Or it might be just me not used to it, so I'm happy either way 😁

Copy link
Member
@reisingerf reisingerf left a comment

Choose a reason for hiding this comment

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

Minor comments.
Otherwise LGTM

@@ -76,7 +76,7 @@ export const rdsMasterSecretName = 'orcabus/master-rds'; // pragma: allowlist se
validateSecretName(rdsMasterSecretName);

// Other constants that exist in the SharedStack
export const regName = 'OrcaBusSchemaRegistry';
export const regName = 'orcabus.events';
Copy link
Member

Choose a reason for hiding this comment

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

I don't think we have other registries planned, but can we be a bit more specific?
E.g. eventRegName or schemaRegName

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, I will change it to schemaRegistryName

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed with efd9a5b

Comment on lines +62 to +63
"startTime",
"endTime",
Copy link
Member

Choose a reason for hiding this comment

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

You are keeping one record for each SequenceRun, right?
(i.e. there are defined start/end times and no intermediate state-bound times)

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, that right. One record for each run; unique by instrumentRunId.

* Removed POC code comment from constants
@victorskl
Copy link
Member Author

preference of having as close as possible to the code

Good point, Will. Schema is a bit tricky. Schema is a contract documentation by definition. Putting under docs section emphasizes this point. We might probably using some doc generator on these schemas to present them to user or observer, at some point down track. So, these folks won't need to dig through our code base, too much.

@victorskl
Copy link
Member Author

Alexis; Ray; going to merge this now. Comment if any.

@victorskl victorskl merged commit 7ae942d into main May 3, 2024
2 checks passed
@victorskl victorskl deleted the refactor-event-schema branch May 3, 2024 08:27
@victorskl victorskl linked an issue May 3, 2024 that may be closed by this pull request
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.

Review and finalise event schema
3 participants
0