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

Auto-Synthesize Ingestion Package Import.Yaml Files #63

Open
chrisage opened this issue May 24, 2023 · 2 comments · May be fixed by #186
Open

Auto-Synthesize Ingestion Package Import.Yaml Files #63

chrisage opened this issue May 24, 2023 · 2 comments · May be fixed by #186
Assignees
Labels
enhancement New feature or request

Comments

@chrisage
Copy link
Contributor

chrisage commented May 24, 2023

Related Auto-Synthesize Manifest Files: #10

Background:
To promote rapid RACK development we want a feature that will auto-updates RACK reference resources (data, model, nodegroups yamls/csvs) when a project is updated.

Acceptance Criteria:
When a button is clicked in RITE, all import yamls within the workspace should be updated with corresponding resource types e.g.

  • store_data.csv updated when nodegroups folder has a file added / deleted
  • data.yaml updated when data folder has a file added / deleted
  • model.yaml updated when a model folder has a file added / deleted

Implementation Details:
TBD

@saratge
Copy link
Contributor

saratge commented May 25, 2023

  • I tested the re-generate manifests feature, I finally understand it. The Regenerate manifest feature assumes a project might have a model.yaml, data.yaml or a store_data.csv respectively identifying owl, csv or nodegroup json.

  • The regenerate manifest feature also respects project references, which allows for modular project creation in RITE

  • Given that we have locked the story for PI demo Finalize the demo story for the PI meeting #56 (comment)
    we can move this out of scope for RITE PI demo

  • We may still keep this in scope for June 5th RITE release

@chrisage
Copy link
Contributor Author

chrisage commented May 31, 2023

We may need to re-design the workflow for auto-generating yamls to be more active using validations on the yamls rather than users searching to classify files

e.g. if a project is marked as a RACK project, validations are activated based on the structure of the project. One validation might be: data.yamls have to include references to all .csv files within the same dir (commented out to disable)

@davidcok davidcok linked a pull request Mar 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants