[Bug]: get actor-template -o yaml prints a ListActorTemplatesResponse envelope that create actor-template -f rejects
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 78/100
Research direction
Start with cmd/kubectl-ate/internal/printer/printer.go around lines 296-300 and cmd/kubectl-ate/internal/cmd/create_actor_template.go around lines 82-84. Reproduce the documented get -o yaml and create -f commands, then inspect the README and --help text for the expected round-trip. Done means YAML emitted by get actor-template can be accepted by create actor-template without the actorTemplates unknown-field error.
Written by the indexing model from the issue text.
Description
kubectl ate get actor-template <name> -a <atespace> -o yaml prints the template wrapped in the ListActorTemplatesResponse envelope, i.e. under a top-level actorTemplates: list key.
kubectl ate create actor-template -f <manifest> parses its input as a bare ateapipb.ActorTemplate with strict protojson (unknown fields are an error). It therefore rejects exactly the document the get command just printed:
Error: failed to parse actor template manifest "template.yaml": proto: (line 1:2): unknown field "actorTemplates"
Both the README and the command's own --help text tell users that the -o yaml output can be fed back in, so the documented get -> edit -> re-apply round-trip does not work.
actor-template is the only noun in kubectl-ate that accepts -f, so it is the only noun where this round-trip is offered, and it is broken.
Verified at 58624ee8.
- Dominant language
- Go
- Stars
- 2k
- Forks
- 333
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 275
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from agent-substrate/substrate
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agent-substrate/substrate#1750 · 1 comment ·
-
area/dev-infra area/microVM kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agent-substrate/substrate#1695 · 2 comments ·
-
area/node area/observability good first issue kind/feature prio/P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agent-substrate/substrate#1647 · 1 comment ·
-
area/demos kind/bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
agent-substrate/substrate#1579 · 1 comment ·
-
area/network kind/bug kind/docs prio/P0
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
agent-substrate/substrate#1525 ·
All issues in agent-substrate/substrate
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100