Add on/off toggle setting to control project visibility as catalog resource in catalog
Summary
Currently, as a part of #415289 (closed), we have a database column called catalog_resources.state which captures whether a project's catalog resources are not published (aka draft) stored as 0 or published stored as 1. If set as 0, it means that currently, a user does not have a way to change it to published (1) because it gets initially set when creating a project (i.e. prompt asking if user wants to mark this project as a catalog resource, noting this action is not reversible).
Proposal
By creating a project setting toggle to control the project visibility as a catalog resource as on (catalog_resources.state = 1) or off (catalog_resources.state = 0), it would allow users the ability to go back and forth between when a component without a project, and its resources can be discovered in the catalog or not.
Questions to consider ❓ ❓
Question: Do we know if we want to destroy all catalog resource-related records if the user toggles it to OFF? Question: If a user toggles something off, then on, do they then get a fresh start? If so, should that mean we should not destroy any resources?
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
| Group | Issue Link |
|---|---|
| backend | #415289 (closed) |
| backend frontend |
|