-
Notifications
You must be signed in to change notification settings - Fork 70
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
Conversation
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 ? |
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 |
Also, we typically release-note changes to the spec docs, even if they're minor clarifications. |
@travier, are you planning to handle updating this? |
I need to update it and sync it with the Ignition docs. Open to someone else picking it up. |
def7bc0
to
2414219
Compare
There was a problem hiding this 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.
851f0e7
to
e1af6ef
Compare
0e16803
to
543e55f
Compare
There was a problem hiding this 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
.
Additionally clarify that `hash` fields describe the decompressed contents. Co-authored-by: Timothée Ravier <tim@siosm.fr>
Thanks @prestist ! |
No description provided.