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
As per RFC current deploy request accepts only for a single namespace, in a single api call we need to support deployment of single/multiple/all namespaces instead of limiting to single namespace.
Out of Scope
Integrating with the new flow.
The text was updated successfully, but these errors were encountered:
sravankorumilli
changed the title
Optimus CLI & API should Support Deployment of Single/Multiple Namespaces
CLI & API should Support Deployment of Single/Multiple Namespaces
Feb 25, 2022
Some tech debt we encountered during make a changes:
Need namespace convention if we want to deploy multiple namespaces -> cli command can't accept multiple value, unless we split by comma separated
Possibility for jobSpecRepo is nil this loc, but there's no nil checking in command jobCommand, etc that use jobSpecRepo eg this loc
jobCommand should accept namespace as required. We assume we won't able to run optimus create job without specifiying namespace. (job creation can't happen in root)
@sravankorumilli@deryrahman@irainia is there a possibility of job deployment without specifying specific namespace? For example empty namespace or [*] namespace means all namespaces in a project.
As per RFC current deploy request accepts only for a single namespace, in a single api call we need to support deployment of single/multiple/all namespaces instead of limiting to single namespace.
Out of Scope
The text was updated successfully, but these errors were encountered: