resources table schema

[anonymoussprocket]

Column	Data Type	Description
resourceid	numeric, primary key	sequence auto-increment pk
resourcename	text, not null
description	text, not null
platform	text, not null	'Conseil', 'Tezos', etc
network	text, not null	'prod', 'mainnet', etc

[vishakh]

Could you define what a resource is and how it is used?

[anonymoussprocket]

A dev Conseil instance, an alphanet Tezos node instance, etc.

[vishakh]

And how would these records be used?

[leenpaws]

If i'm getting this correctly, it's essentially an inventory of what's available (i.e. bandwith, unused instances, open api key, etc.)

[vishakh]

@anonymoussprocket Could you confirm what @leenpaws said?

[ivanopagano]

Is there supposed to be a relationship table somewhere between api-keys and resources?

Personally I don't see api-keys as valid resources in this table

[anonymoussprocket]

API keys are provisioned for services (resources). Is this API key allowed to query Conseil? Is this API key allowed to query Tezos.

[ivanopagano]

API keys are provisioned for services (resources). Is this API key allowed to query Conseil? Is this API key allowed to query Tezos.

Now that I looked again at the apikey table I get it

[ivanopagano]

I was curious to know if there's a real advantage in using the tablename inside columns as in:

• resourceid
• resourcename

Is it a best-practice for db-admins reasons that I'm ignorant of?

p.s. I can see this as a useful ambiguity-resolver when joining many tables that share common column-names like id, name, description, ...