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
{{ message }}
This repository has been archived by the owner on Jul 13, 2021. It is now read-only.
I've finished oamctl trait-list, I'm wondering do we really need a command like oamctl create -c ./config.yaml ./frontend.yaml ./backend.yaml -p "message=overridden message!"
Think further, implement oamctl create means we'll need to invoke API from OAM runtime. Now we have rudr which use K8s APIServer, what if another OAM runtime not using K8s APIServer? We may need to adapt lots APIServer unless we give a unified APIServer.
So I suggest use kubectl in the current time untill we have a different APIServer. In that time, we should consider should we make a unified APIServer including authorization, rest api for CRUD, etc..
https://github.com/oam-dev/spec/blob/master/6.application_configuration.md#an-example-workflow
Install
Discovery
The text was updated successfully, but these errors were encountered: