[Model WatchTower] Reduce exposure of Links logic

[avishniakov]

Describe changes

I kept only the List functionality public for links. Creates and deletes will go only via SQL Store.
I kept one test running on the Rest Store - query empty list. Not sure, if I can somehow populate the list by switching to SQL for that purpose. If this is doable - guidance is appreciated.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• If my change requires a change to docs, I have updated the documentation accordingly.
• If I have added an integration, I have updated the integrations table and the corresponding website section.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[avishniakov]

@fa9r @strickvl as requested 🙂

[avishniakov]

I have a question about Zen Stores:

• I removed REST endpoints to create or delete links between Model Version and Artifacts to reduce exposure to very internal logic
• I'm working on a class to be used in Annotation of step outputs
• This class will have link_to_model method and inside I call Client().zen_store.creaate_.._link(...)

I imagine, that there is no warranty that this code will be executed towards SQL store, if used by Step Exit logic. Am I wrong and there is nothing to worry about? If I'm not wrong, how to ensure SQL execution?

Moreover: I start to get a headache once I imagine what should happen, if user is running on local stack connected to a remote server...

Help needed 🙂

[avishniakov]

Closing as not feasible at the moment.