Skip to content

SPEC, libcni: harmonize GC valid-attachment key - #1103

Merged
squeed merged 2 commits into
containernetworking:mainfrom
squeed:fix-gc-key-name
Jul 22, 2024
Merged

SPEC, libcni: harmonize GC valid-attachment key#1103
squeed merged 2 commits into
containernetworking:mainfrom
squeed:fix-gc-key-name

Conversation

@squeed

@squeed squeed commented Jul 1, 2024

Copy link
Copy Markdown
Member

The SPEC said valid attachments should be cni.dev/attachments, whereas libcni used cni.dev/valid-attachments. Oops.

This changes the SPEC to match libcni, and has libcni set both variables, just in case.

Fixes: #1101

The SPEC and libcni disagreed on the name to use for still-valid
attachments. Change the spec to be aligned with libcni.

Signed-off-by: Casey Callendrello <c1@caseyc.net>
@squeed

squeed commented Jul 1, 2024

Copy link
Copy Markdown
Member Author

@kanpov thanks for noticing this!

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 63.78% (+0.03%) from 63.753%
when pulling ae9487b on squeed:fix-gc-key-name
into d5c71ad on containernetworking:main.

Comment thread libcni/api.go
Comment thread SPEC.md
I made an (embarassing) error where SPEC.md and libcni disagreed on the
key for valid attachments for a GC operation. The spec has been
updated, but libcni should set both keys as a transition mechanism.

Signed-off-by: Casey Callendrello <c1@caseyc.net>
@squeed
squeed force-pushed the fix-gc-key-name branch from ae9487b to 692efbd Compare July 22, 2024 14:57
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 63.78% (+0.03%) from 63.753%
when pulling 692efbd on squeed:fix-gc-key-name
into d5c71ad on containernetworking:main.

@squeed
squeed merged commit 309b6bb into containernetworking:main Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error in specification regarding GC??

5 participants