Why `cloud=k8s` is hard-coded in the `Ballerina.toml` file?
sameerajayasoma opened this issue · 2 comments
sameerajayasoma commented
We can update the build scripts to include the cloud=k8s option when building the package. When this option is included in the Ballerina.toml file, every bal build invocation attempts to create k8s artifacts, which is annoying in regular development time.
dilanSachi commented
Yes it's better to add cloud option to build scripts
xlight05 commented
@sameerajayasoma I agree.
The only reason why we had it because we thought that the scenario is built to run on k8s. Since considerable number of services depends on other services, the developemnt was done using all the services(which requires containers). However as a practice I think what you are saying makes sense, we need the boundary between local development and cloud build.