Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Fix 'config' mention in 'hash' docs #387

Merged
merged 1 commit into from
Mar 4, 2023

Conversation

travier
Copy link
Member

@travier travier commented Sep 19, 2022

No description provided.

@travier
Copy link
Member Author

travier commented Sep 19, 2022

How do we feel about adding a note like "If compression is set, then the hash is for the decompressed content" to all of those instances for coreos/ignition#961 ?

@travier travier added the skip-notes This PR does not need release notes label Sep 19, 2022
@bgilbert
Copy link
Contributor

Let's aim to keep the Butane spec docs in sync with the Ignition ones. The Ignition spec docs opted for "the hash of the contents", which is a little clearer in the context of the spec.

"If compression is specified, the hash describes the decompressed contents" SGTM.

@bgilbert
Copy link
Contributor

Also, we typically release-note changes to the spec docs, even if they're minor clarifications.

@bgilbert bgilbert removed the skip-notes This PR does not need release notes label Sep 22, 2022
@bgilbert
Copy link
Contributor

@travier, are you planning to handle updating this?

@travier
Copy link
Member Author

travier commented Oct 25, 2022

I need to update it and sync it with the Ignition docs. Open to someone else picking it up.

@prestist prestist force-pushed the hash-files branch 3 times, most recently from def7bc0 to 2414219 Compare March 2, 2023 22:24
Copy link
Contributor

@bgilbert bgilbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need the "decompressed contents" note on the other hash fields too. Ignition spec docs will need a similar update.

docs/config-fcos-v1_0.md Outdated Show resolved Hide resolved
docs/release-notes.md Outdated Show resolved Hide resolved
@prestist prestist force-pushed the hash-files branch 3 times, most recently from 851f0e7 to e1af6ef Compare March 3, 2023 14:11
@prestist prestist changed the title docs: Fix 'config' mention in 'hash' doc for files & keyfiles docs: Fix 'config' mention in 'hash' docs Mar 3, 2023
@prestist prestist force-pushed the hash-files branch 3 times, most recently from 0e16803 to 543e55f Compare March 3, 2023 14:40
Copy link
Contributor

@bgilbert bgilbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The certificate_authorities hash fields generally need to add the sentence about compression.

docs/release-notes.md Outdated Show resolved Hide resolved
docs/config-openshift-v4_12.md Outdated Show resolved Hide resolved
docs/config-openshift-v4_12.md Outdated Show resolved Hide resolved
docs/config-r4e-v1_0.md Outdated Show resolved Hide resolved
docs/config-r4e-v1_0.md Outdated Show resolved Hide resolved
docs/config-r4e-v1_1-exp.md Outdated Show resolved Hide resolved
docs/config-r4e-v1_1-exp.md Outdated Show resolved Hide resolved
Additionally clarify that `hash` fields describe the decompressed contents.

Co-authored-by: Timothée Ravier <tim@siosm.fr>
@prestist prestist merged commit 17e4af7 into coreos:main Mar 4, 2023
@travier travier deleted the hash-files branch March 6, 2023 09:46
@travier
Copy link
Member Author

travier commented Mar 6, 2023

Thanks @prestist !

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.

3 participants