switch to natsjs registry

[wkloucek]

Description

update oCIS to latest master and switch to natsjs registry

Related Issue

• Makes use of Natsjs registry ocis#7487

Motivation and Context

How Has This Been Tested?

• run the nats deployment example in minikube

Screenshots (if appropriate):

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)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation generated (make docs) and committed
• Documentation ticket raised:
• Documentation PR created:

[wkloucek]

@kobergj while implementing this I noticed, that store and cache support nats-js while registry now supports a natsjs option. Probably those options should have the same name for the oCIS 5 release, right?

[kobergj]

Yes I saw that too when I was poking around in the helmchart. Let's unify them. Which one should we use? nats-js or natsjs?

[kobergj]

Nice 👍

[wkloucek]

Yes I saw that too when I was poking around in the helmchart. Let's unify them. Which one should we use? nats-js or natsjs?

The majority so far uses nats-js (store + cache). Changing them would be a breaking change?