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

write an RFC for graph deprecation schema/validation #1146

Closed
grokspawn opened this issue Oct 10, 2023 · 2 comments
Closed

write an RFC for graph deprecation schema/validation #1146

grokspawn opened this issue Oct 10, 2023 · 2 comments

Comments

@grokspawn
Copy link
Contributor

Write an RFC based on brief to develop a shared design intent on graph deprecation

Acceptance Criteria

  • satisfies functional requirements of brief
  • documents interface/UX changes
  • identifies documentation impacts
  • is reviewed and approved
@grokspawn
Copy link
Contributor Author

grokspawn commented Oct 23, 2023

Doc here

Implementation areas

  1. schema def, parsing (alpha/declcfg/declcfg.go, utests)
  2. validation command update (alpha/model/model.go, utests) (killed this since validation will be handled as part of model conversion for GRPC API updates)
  3. visualization update (cmd/opm/alpha/render-graph/cmd.go..., utests)
  4. GRPC API (pkg/registry/types.go, utests)
  5. migrate command update (not clear if we need this) <-- we could implement later to service migration from sqlite catalog formats (olm.deprecated & olm.substitutesfor) (killed this since the previous expression of 'deprecated' meant 'uninstallable' and there's not enough strong inference to convert to the new meaning)

@grokspawn
Copy link
Contributor Author

Matured by consensus date

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

No branches or pull requests

1 participant