Dharmit Shah
Dharmit Shah
Before doing this, we first need to figure out a way to show the user the list of containers and segregate them to Dev mode or Deploy mode. /area log
> We've looked into several ways to approach this issue: > > 1. `odo logs --list-containers` that lists containers before user can decide which container, and then run `odo logs...
@kadel we had a bunch of conversation around this in the last backlog grooming call. One of the things you mentioned was to let multiple users be able to do...
Notes from the discussion on this in the odo contributors' call: 1. This should ideally be addressed at Devfile API level such that a `container` component has a `serviceAccount` attribute....
https://github.com/devfile/api/blob/fe7c10eaa530b12b19cfb0e22e221e753391304c/pkg/attributes/attributes.go#L14
@feloy running `odo dev` from this PR doesn't store the port information in the state file. I think that's a regression, right?
We also need to update the [env file](https://odo.dev/docs/command-reference/dev#env-file) section of the docs to reflect the changes made here, no?
@feloy I think this warning message shouldn't be printed anymore. If I wanted to deploy my component in a particular namespace, this is _the_ way to do it, since the...
What I am describing below was purposefully done to break stuff. I first created an Operator backed service in the namespace `myproject`. 1. `odo dev` in dir1. Component gets pushed...
> I tested it but cannot reproduce. Can you share the steps to reproduce? @feloy my bad. I was looking into `env.yaml` instead of `devstate.json`. me--. 😞