Skip to content

Frontend: Add the new tab "components" as experimental feature

Update

We are going to release this feature as experimental as noted in #438066 (closed) we might stop collecting Meta data automatically and this feature might stop working

Summary

Add the new tab components as a second tab in the Catalog details page. The default will remain the README tab.

Proposal

From the discussion in number 3 in #415657[Details-inputs-table-v2.png], the intention here is to add the new tab components.

Additional details

Some relevant technical details, if applicable, such as:

  • Does this need a feature flag?
  • Does there need to be an associated instrumentation issue created related to this work?
  • Is there an example response showing the data structure that should be returned (new endpoints only)?
  • What permissions should be used?
  • Is this EE or CE?
    • EE
    • CE
  • Additional comments:

Implementation Table

NOTE: Backend: Create a migration to update state and... (#416292 - closed) can (and should) be worked on immediately after Backend: Scan a catalog resource for components (#415413 - closed)

Group Issue Link
backend Backend: Add components field to ciCatalogResou... (#425726 - closed)
frontend 👈 You are here
backend Backend: Scan a catalog resource for components (#415413 - closed)
backend Backend: Create a migration to update state and... (#416292 - closed)
backend Backend: Add `path` of the component to db (#427170 - closed)
backend Backend: Add path field to ciCatalogResourceCom... (#427169 - closed)
backend Backend: Update the CI Catalog index to only sh... (#415414 - closed)
backend Add `components` field, ComponentType and Input... (!136074 - merged)
frontend Update CI/CD catalog components tab with real data (!138217 - merged)

Links/References

Edited by Dov Hershkovitch