Exechook commands

[tomasz-sulek-atos]

Is is possible somehow by any syntax to run exechook command with an argument ?

[thockin]

Strictly speaking, no. What argument do you want to pass? Something static or something dynamic from the current state?

[tomasz-sulek-atos]

static, just flags

[thockin]

Is there a reason you can't just bake those into a no-args script?

What I want to avoid is parsing args with shell-ish semantics. E.g. --exechook-args="a string \"with quotes\" -- is that 2 or 3 args? Not impossible, but it's not something we support today.

A simpler approach might be --exechook-arg="a" --exechook-arg="string" --exechook-arg="with quotes"

I am not going to have time in the near future, but I am open to shepherding contributions.

[tomasz-sulek-atos]

Have you considered to use json/yaml for specify commands and argument like we do in DockerFiles ?

[thockin]

That seems like overkill. Flags can be made to work, I think.

[tomasz-sulek-atos]

Why overkill ? If you use a json list you don't have any shell semantics issues

[thockin]

If you want an unambiguous list of strings, just use string-list (repeated) flag or define a string parser. Why introduce a new config mechanism that still requires parsing anyway? It just doesn't do anyther better than a simple approach would.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale