Learn about Kebechet managers used in specific repos

[pacospace]

Is your feature request related to a problem? Please describe.

Currently, we know when a user is installing Kebechet and if it is active or not, so that we can provide services accordingly.

But we don't have a way to store information about which managers are active. Moreover, if the user deactivates a certain manager would be also interesting to know.

[pacospace]

Related-to: thoth-station/metrics-exporter#559
Related-to: thoth-station/kebechet#546

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[pacospace]

/remove-lifecycle stale

[goern]

/triage needs-information
/sig observability

[KPostOffice]

https://github.com/thoth-station/thoth-application/blob/master/kebechet/overlays/test/kebechet.yaml

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pacospace]

@KPostOffice is this something we can do already?

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[KPostOffice]

@pacospace This is actually present in storages. We store each manager as a boolean column for the installation. Here is a query which uses it. https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3890
We want to get a count of how many instances of each manager we find in the database right?

[pacospace]

@pacospace This is actually present in storages. We store each manager as a boolean column for the installation. Here is a query which uses it. https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3890 We want to get a count of how many instances of each manager we find in the database right?

should we add a distinct in that query? because a slug can have multiple runtime environments right?

[KPostOffice]

https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3917

We grab just the first

[pacospace]

https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3917

We grab just the first

Sorry, then good :)

[pacospace]

@pacospace This is actually present in storages. We store each manager as a boolean column for the installation. Here is a query which uses it. https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3890 We want to get a count of how many instances of each manager we find in the database right?

Yes, don't we have a query for that?

[KPostOffice]

@pacospace This is actually present in storages. We store each manager as a boolean column for the installation. Here is a query which uses it. https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3890 We want to get a count of how many instances of each manager we find in the database right?

Yes, don't we have a query for that?

Yeah you are right. It is right here

[pacospace]

@pacospace This is actually present in storages. We store each manager as a boolean column for the installation. Here is a query which uses it. https://github.com/thoth-station/storages/blob/6cf9c2c05d02c698bb8ad8641146cd1dab582fe6/thoth/storages/graph/postgres.py#L3890 We want to get a count of how many instances of each manager we find in the database right?

Yes, don't we have a query for that?

Yeah you are right. It is right here

Then I think we can close this issue right?

[goern]

/close

[sesheta]

@goern: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.