-
Notifications
You must be signed in to change notification settings - Fork 166
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
Document Trusted Builders #167
Comments
I would add to "What questions should this documentation answer?":
|
One thing to keep in mind is that this feature is specific to |
Hmm. But it did go through the RFC/spec process, and it is formally added to the spec, so it's a bit more broad than only pack, though in implementation it is only used by |
With #161, we should have a section for pack! |
I see the RFC (buildpacks/rfcs#46) that you might be referencing but it's more about |
Ah never mind, with the spec, I was thinking about the project descriptor (#165 ). |
But I do think it is important, particularly given the presence of trusted builders in our commands and logs, to have some good and clear documentation around it |
The split between pack/buildpacks/lifecycle in the docs is an interesting/difficult one, because in practice most of the docs site is for pack (for instance, all of the guides are leading through pack commands). |
Summary
We now have a concept of a trusted builder, and we should document it.
What questions should this documentation answer?
Who is the target audience for this documentation?
Additional Information
Relevant RFCs:
Relevant Pack PRs:
analyze
,restore
, andexport
in an ephemeral image pack#631Relevant articles:
The text was updated successfully, but these errors were encountered: