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

JSON Artifacts: Common metadata field #2761

Closed
beckjake opened this issue Sep 16, 2020 · 0 comments · Fixed by #2778
Closed

JSON Artifacts: Common metadata field #2761

beckjake opened this issue Sep 16, 2020 · 0 comments · Fixed by #2778
Labels
1.0.0 Issues related to the 1.0.0 release of dbt artifacts enhancement New feature or request

Comments

@beckjake
Copy link
Contributor

Describe the feature

All JSON artifacts (catalog.json, manifest.json, sources.json, and run_results.json) should have common metadata fields. Those metadata fields should contain the common metadata that all fields have. Eventually (once everything in #2671 is implemented), I'd expect it to be:

  • invocation_id
  • dbt version
  • dbt_schema_version
  • the env metadata fields
  • generated_at

There should also be artifact-specific metadata fields. For example, the existing metadata field in the manifest can be added to the above fields, just for the manifest.

Depending upon the order we do this in relative to other json artifact issues, some of the fields listed above might not exist. That's ok!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.0.0 Issues related to the 1.0.0 release of dbt artifacts enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants