For the cli, we should use kubectl approach
Create a .invok/invok-cli.config.yaml in the host home directory.
⁸
Introduce 3 new commands:
A. Create context (you can rename this), which takes the context name and the server host url. If there's no existing default context, make that the default
B. List contexts
C. Remove context
D. Set default context to the context name specified.
So every cli operation reads the default context and uses that server url, auth details, etc to execute the command
Also this config should be stored in yaml, it's much more readable than json, same for ever config in the system. You'll have to change serde_json to serde_yaml
P.S can we remove the second config.json that's created at root level, it's highly confusing and not necessary. The config.json created for each function should contain all the information necessary to deploy that function.
For the cli, we should use kubectl approach
Create a
.invok/invok-cli.config.yamlin the host home directory.⁸
Introduce 3 new commands:
A. Create context (you can rename this), which takes the context name and the server host url. If there's no existing default context, make that the default
B. List contexts
C. Remove context
D. Set default context to the context name specified.
So every cli operation reads the default context and uses that server url, auth details, etc to execute the command
Also this config should be stored in yaml, it's much more readable than json, same for ever config in the system. You'll have to change
serde_jsontoserde_yamlP.S can we remove the second config.json that's created at root level, it's highly confusing and not necessary. The config.json created for each function should contain all the information necessary to deploy that function.