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

[FEATURE] Extension Methods and Models to interact with streams #106

Open
jrbentzon opened this issue Sep 24, 2024 · 1 comment
Open

[FEATURE] Extension Methods and Models to interact with streams #106

jrbentzon opened this issue Sep 24, 2024 · 1 comment
Labels
code/new-feature New feature or request

Comments

@jrbentzon
Copy link
Member

jrbentzon commented Sep 24, 2024

Description

When interacting with streams, we set annotations. To to this extensively from external services we need to load the kubernetes objects, interpret them and annotate them. It would be helpful to have framework methods to aid this process.

Possible solution

Extension methods / service to manipulate Arcane based kubernetes resources.

E.g.:,

cluster.GetStreamDefinition(myNamespace, myStreamKind, myApiVersion)
  .Annotate(ArcaneStatus.RELOAD_REQUESTED);

or

cluster.GetStreamDefinition(myNamespace, myStreamKind, myApiVersion)
  .RequestReload()

Alternatives

Move IStreamDefinition & StreamDefinition to Arcane.Framework

Context

We'd like add features for our clients to request restarts / reloads / etc to streams from UI and need to implement a bridge-service to handle interaction between Customer Backend and Arcane

@jrbentzon jrbentzon added the code/new-feature New feature or request label Sep 24, 2024
@s-vitaliy s-vitaliy added this to Arcane Sep 25, 2024
@s-vitaliy
Copy link
Contributor

s-vitaliy commented Sep 25, 2024

We should create a separate package with name like Arcane.Client, Arcane.Facade or so and create required models/functions there. Moving IStreamDefinition & StreamDefinition to Arcane.Framework could potentially cause confusion between the StreamDefinition and StreamContext classes, which I would prefer to avoid.

@s-vitaliy s-vitaliy moved this to Backlog in Arcane Sep 25, 2024
@s-vitaliy s-vitaliy assigned s-vitaliy and unassigned s-vitaliy Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/new-feature New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants