You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is really nothing specific in the deployment architecture that's required to support multi-tenancy - just a new rev of the task image to include the code that enables it.
Some logistics of course need to be performed if the move to multi-tenancy is performed in the current JPL AWS environment - namely the removal of remotes from the EN Opensearch domain (which activates the use of CCS in the registry service). I don't see a reason to remove the implementation supporting CCS since there could be cases where it could be usefully leveraged - as long as it is deactivated as above, there is no adverse effect to performance or stability.
As correctly indicated in the description, this is superseded by registry-185 so I am going to close this one. Feel free to re-open if any of my comments/assumptions made in the previous comment are invalid or questionable.
💡 Description
TBD description of what needs to be updated. May be superseded by #186
The text was updated successfully, but these errors were encountered: