Skip to content

chore: Move chef-cli docs to fern #186

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 28 commits into from
Apr 1, 2025
Merged

chore: Move chef-cli docs to fern #186

merged 28 commits into from
Apr 1, 2025

Conversation

tilenkavcic
Copy link
Contributor

@tilenkavcic tilenkavcic commented Mar 29, 2025

This brings in documentation from the chef-cli repository. This first version improves metadata extraction and adds IDM.
There is also a framework do add the rest under the Data model folder, but this is hidden for now.

https://app.devrev.ai/devrev/works/ISS-154217

Copy link
Contributor

github-actions bot commented Mar 29, 2025

🌟 EkLine Reviewer

Hello! I’m here to help improve your docs. I’ve reviewed your pull request, and left in-line suggestions for quick fixes. For details, visit the Analytics Page.

For questions or feedback, please email support@ekline.io.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

EkLine

🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- [jq](https://stedolan.github.io/jq)


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- [golang](https://go.dev/doc/install)


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- [nodejs](https://nodejs.org/en/download/package-manager) (version 18.x.x+ or higher)


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

1. Create an import at **Settings** > **Imports** > **Import**.

Copy link
Contributor

Copy link
Contributor

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

EkLine

⚠️ [EkLine] reported by reviewdog 🐶

Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)

This mapping, unlike the recipe blueprint of a concrete import, can contain multiple options for each external record type from which the end-user might choose (for example allow *task* from an external system to map either to *issue* or *ticket* in DevRev), and it can contain also mappings that apply to a record type category. When the user runs a new import, and the extractor reports in its metadata record types belonging to this category, that are not directly mapped in the initial domain mappings, the recipe manager will apply the per-category default to them.


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- raw jq transformations using an external field as input. (This is an experimental feature)


⚠️ [EkLine] reported by reviewdog 🐶

Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)

This will output any problems there may be with the metadata file.


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Contain the same type of records, named after their type


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Have .json or .jsonl extension, for example `issues.json`


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Contain either a single JSON array of objects, or newline-separated objects


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

2. Run the `infer-metadata` command targeting this directory


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

3. Inspect the generated metadata, particularly field types and the suggestions the tool generates


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Provide 10-100 examples of each record type (but not more than 1000)


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Ensure logically distinct fields are separate keys at the top level


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Use referentially consistent example data if possible


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- Make sure IDs are strings, not numbers


⚠️ [EkLine] reported by reviewdog 🐶

Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)

This generated metadata serves as a starting point that will need further refinement. It can be used to prototype initial domain mappings (by running a sync with it) and to generate example normalized data, but it is still just a guess: It has to be reviewed and refined.


⚠️ [EkLine] reported by reviewdog 🐶

Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)

`is_write_only` etc. By default these will be set to false. You can find the full list of supported


🚫 [EkLine] reported by reviewdog 🐶

Prefer English terms over Latin abbreviations. Use 'for example' instead of 'e.g.'. (EK00026)

possible (e.g., to move to the 'resolved' status, an issue first has to be 'in_testing'), you


⚠️ [EkLine] reported by reviewdog 🐶

Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)

This will allow creation of a matching 'stage diagram' (a collection of stages and their permitted


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- The status field is the controlling field of the stage diagram


🚫 [EkLine] reported by reviewdog 🐶

Suggestions:

  • Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)
  • Must put the ending punctuation at the end of a list item. (EK00041)

- If a status field has no explicit transitions but you still want a stage diagram, set `all_transitions_allowed` to `true`, which will create a diagram where all the defined stages can transition to each other


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- External systems may categorize statuses (like Jira's status categories), which can be included in the diagram metadata (`states` in the example)


⚠️ [EkLine] reported by reviewdog 🐶

Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)

- The `starting_stage` defines the initial stage for new object instances. This data should always be provided if available, otherwise the starting stage will be selected alphabetically


🚫 [EkLine] reported by reviewdog 🐶

Must put the ending punctuation at the end of a list item. (EK00041)

- In current metadata format (v0.2.0), the order and human-readable name are taken from the enum values defined on the controlling field


🚫 [EkLine] reported by reviewdog 🐶

Suggestions:

  • Where possible, do not structure sentences in future tense. Use present tense instead. (EK00005)
  • Must put the ending punctuation at the end of a list item. (EK00041)

- If the `states` field is not provided, default DevRev states will be used: `open`, `in_progress` and `closed`

@tilenkavcic tilenkavcic changed the title chore: Move Chef cli docs to fern chore: Move chef-cli docs to fern Mar 29, 2025
Copy link
Contributor

Copy link
Contributor

Copy link
Contributor

Copy link
Contributor

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Copy link
Contributor

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Copy link
Contributor

Copy link
Contributor

@tilenkavcic tilenkavcic marked this pull request as ready for review March 30, 2025 17:05
@tilenkavcic tilenkavcic requested a review from a team as a code owner March 30, 2025 17:05
Copy link
Contributor

Copy link
Contributor

Copy link
Contributor

Copy link
Contributor

@erazemk erazemk left a comment

Choose a reason for hiding this comment

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

There are so many changes I didn't manage to read them all, but the overall gist looks fine

Copy link
Contributor

tilenkavcic and others added 2 commits March 31, 2025 14:11
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Copy link
Contributor

Copy link
Contributor

@tilenkavcic tilenkavcic requested a review from erazemk March 31, 2025 13:02
Copy link
Contributor

@bc-devrev bc-devrev left a comment

Choose a reason for hiding this comment

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

Approved with some suggestions.

Copy link
Contributor

github-actions bot commented Apr 1, 2025

Copy link
Contributor

github-actions bot commented Apr 1, 2025

@tilenkavcic tilenkavcic merged commit a9bc3c9 into main Apr 1, 2025
3 checks passed
@tilenkavcic tilenkavcic deleted the tilenk/chef-cli branch April 1, 2025 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants