- Added new section 'Community learning resources' after Community and Support section
- Includes two third-party learning resources: KodeKloud and Udemy courses
- Added call-to-action for community to suggest additional resources
- Fixed Vale linting issues with proper ignore comments
Signed-off-by: abhi-bhatra <abhinavsharma.cse23@jecrc.ac.in>
May be pedantic, but the link wasn't being rendered correctly due to some annoying spacing issues.
Signed-off-by: William Karavites <wkaravites@gmail.com>
Only include those files that the developer has changed in the
vale lint. This will remove the need to fix _all_ the problems in
content on every commit.
Signed-off-by: adelaney21 <adelaney21@bloomberg.net>
The `launch.toml` command takes a slice and not a string
```
remote: ERROR: failed to build: toml: line 3 (last key "processes.command"): incompatible types: TOML value has type string; destination has type slice
```
Spec: d29ba81518/buildpack.md (launchtoml-toml)
Signed-off-by: Richard Schneeman <richard.schneeman+no-recruiters@gmail.com>
* Clear up `clean-env` docs
## Context
I was asked to validate that several buildpacks were correctly passing user-supplied environment variables to sub-processes for the purpose of configuring access to dependencies that require credentials.
The docs clearly state that a `buildpack.toml` with `clear-env` should have specific behavior regarding environment variable visibility, but it's not clear that it means that the `CNB_PLATFORM_DIR/env/` is ALWAYS provided and that `clear-env = false` means that information is merged into the current environment.
If you read it literally and you know that `$CNB_PLATFORM_DIR/env/` is a mechanism to provide the environment variables to a buildpack, you might interpret it as the ability to hide these platform envs from the buildpack. When really, it's saying "lifecycle will make things easy for you if you just want a firehose of all the envs, it will copy the user-provided ones into the current environment so you don't need to." It does this by default with the ability to opt out by setting `clear-env = true`.
## Change
I'm suggesting we tighten up the language here to make it clear that `$CNB_PLATFORM_DIR/env/` is always available, and that setting `clear-env = true` will tell the lifecycle to copy the contents of `CNB_PLATFORM_DIR/env/` into the current environment. Specific language suggestions pending. This logic is in several places:
- https://buildpacks.io/docs/for-buildpack-authors/how-to/write-buildpacks/clear-env/
- https://buildpacks.io/docs/reference/config/buildpack-config/
- https://buildpacks.io/docs/for-app-developers/how-to/build-inputs/configure-build-time-environment/
Signed-off-by: Schneems <richard.schneeman+foo@gmail.com>
* Fix vale failures
Signed-off-by: Schneems <richard.schneeman+foo@gmail.com>
---------
Signed-off-by: Schneems <richard.schneeman+foo@gmail.com>
* Updated the tekton documentation to use the new buildpack task supporting the extension. #814
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Add additional words to vale dictionary
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Extend the documentation to have a chapter covering extension. Add new pipeline parameters
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Review the scenario and tested it using ubi8 and jammy builder images
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Fix some vale vocabularies
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Remove the cache workspace as not used and documented part of task's documentation
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Switch the builder image to use: cnbs/sample-builder
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
---------
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
* Provide an explanation regarding performance degradation when using the Docker daemon with containerd storage.
Signed-off-by: Hiroshi Hayakawa <hhiroshell@gmail.com>
* Add "containerd" to the Vale vocabulary list.
Signed-off-by: Hiroshi Hayakawa <hhiroshell@gmail.com>
* Make the phrasing more friendly for casual users.
Co-authored-by: Aidan Delaney <aidan.delaney@gmail.com>
Signed-off-by: Hiroshi Hayakawa <hhiroshell@gmail.com>
---------
Signed-off-by: Hiroshi Hayakawa <hhiroshell@gmail.com>
Co-authored-by: Aidan Delaney <aidan.delaney@gmail.com>
* Chore: Upgrade jquery and axios version
Signed-off-by: Muneeb Mohammed <muneeb.mohammed@muneebm-ltmeu4b.internal.salesforce.com>
---------
Signed-off-by: Muneeb Mohammed <muneeb.mohammed@muneebm-ltmeu4b.internal.salesforce.com>
Co-authored-by: Muneeb Mohammed <muneeb.mohammed@muneebm-ltmeu4b.internal.salesforce.com>
* Prefer targets over stacks
When creating a new buildpack, use --targets instead of the
deprecated --stacks
Signed-off-by: Aidan Delaney <adelaney21@bloomberg.net>
* Migrated to latest hugo toCSS
Update from deprecated hugo function
Signed-off-by: Aidan Delaney <aidan.delaney@gmail.com>
---------
Signed-off-by: Aidan Delaney <adelaney21@bloomberg.net>
Signed-off-by: Aidan Delaney <aidan.delaney@gmail.com>
* Bump pack version in CI
Update to pack 0.36.0
Signed-off-by: Aidan Delaney <adelaney21@bloomberg.net>
* Update tools to latest pack
Do not require an older dependency
Signed-off-by: Aidan Delaney <aidan.delaney@gmail.com>
---------
Signed-off-by: Aidan Delaney <aidan.delaney@gmail.com>
When a Mac users exports the artifacts built by the `builder`, the
`launcher` executable packaged into an OCI image must be linux arm64 in
the tutorial.
Signed-off-by: Robert Gogolok <robert.gogolok@stackit.cloud>
Aidan Delaney