Christian Himpe

@lvca I see. Then please close my proposed pull request. Two follow questions arise for me then: 1. How should the error starting this issue be handled, meaning an `UPDATE`...

`APPLY DEFAULTS` is a cool idea. That would solve my problem in a non-insular fashion.

Using `BUCKET:myparam` also errors ``` Error on command execution (PostQueryHandler) com.arcadedb.exception.SchemaException: Bucket with name 'myparam' was not found at com.arcadedb.schema.LocalSchema.getBucketByName(LocalSchema.java:281) at com.arcadedb.query.sql.executor.SelectExecutionPlanner.handleClustersAsTarget(SelectExecutionPlanner.java:2196) at com.arcadedb.query.sql.executor.SelectExecutionPlanner.handleFetchFromTarget(SelectExecutionPlanner.java:780) at com.arcadedb.query.sql.executor.SelectExecutionPlanner.createExecutionPlan(SelectExecutionPlanner.java:144) at com.arcadedb.query.sql.parser.SelectStatement.createExecutionPlan(SelectStatement.java:208) at com.arcadedb.query.sql.parser.SelectStatement.execute(SelectStatement.java:201)...

Too bad. So, does this bug report become a feature request or is this too unlikely to be implemented and should hence be closed?

Hmm, so I tried using ``` wget -qO- http://localhost:2480/api/v1/query/test --post-data='{"language":"sql","params":{"myparam":"BUCKET:mybucket"},"command":"SELECT FROM :myparam"}' --user root --password arcadedb ``` which errors, but ``` wget -qO- http://localhost:2480/api/v1/query/test --post-data='{"language":"sql","params":{"myparam":"doc"},"command":"SELECT FROM :myparam"}' --user root --password...

@cdrage @sosan The error is also happening for `kompose 1.33`, but **not** in `kompose 1.32`, if that helps.

I think I have an answer to this issue, and it should affect all secrets not only if there are multiple per service, just in this case it produces an...

/remove-lifecycle stale

/remove-lifecycle stale

This https://github.com/kubernetes/kubernetes/issues/50345 seems to be related.