[GitHub] [camel-k] gansheer commented on issue #3628: Enable CLI completion for integration, kit, kamelet names

2022-12-14 Thread GitBox
gansheer commented on issue #3628: URL: https://github.com/apache/camel-k/issues/3628#issuecomment-1352666197 Hi, > Hi, > > Actually, no, you cannot delete platform kits with `kamel kit delete`. They are protected from cli. There's even no flag to force performing it. So

[GitHub] [camel-k] gansheer commented on issue #3628: Enable CLI completion for integration, kit, kamelet names

2022-12-14 Thread GitBox
gansheer commented on issue #3628: URL: https://github.com/apache/camel-k/issues/3628#issuecomment-1351401902 > I think the general idea was that kits of type `platform` are managed by the operator, as opposed to kits created by users, and should be "hidden" away from users. I get

[GitHub] [camel-k] gansheer commented on issue #3628: Enable CLI completion for integration, kit, kamelet names

2022-12-13 Thread GitBox
gansheer commented on issue #3628: URL: https://github.com/apache/camel-k/issues/3628#issuecomment-1348896623 @tadayosi @squakez What is expected on then `kamel bind` autocomplete ? While we could default to the custom resources `kamelets.camel.apache.org`, the command description

[GitHub] [camel-k] gansheer commented on issue #3628: Enable CLI completion for integration, kit, kamelet names

2022-12-13 Thread GitBox
gansheer commented on issue #3628: URL: https://github.com/apache/camel-k/issues/3628#issuecomment-1348594734 The `kamel kit delete` completion already exists : the command only shows non-platform kits. Is this behavior something that should evolve to all kits (even the platform ones) for