mirror of https://github.com/knative/docs.git
rename sandbox to extensions - manual (#5661)
* rename sandbox to extensiopns - manual * Update config/redirects.yml Co-authored-by: Paul Schweigert <paul@paulschweigert.com> * fix redirect * Update docs/eventing/custom-event-source/custom-event-source/README.md Co-authored-by: Paul Schweigert <paul@paulschweigert.com> * Update docs/community/governance.md Co-authored-by: Paul Schweigert <paul@paulschweigert.com> --------- Co-authored-by: Paul Schweigert <paul@paulschweigert.com>
This commit is contained in:
David Hadas
GitHub
parent
bbe9a0d4c4
commit
115624f392
|
|
@ -56,7 +56,7 @@ plugins:
|
|||
community/contributing/contributing.md: https://github.com/knative/community/blob/main/CONTRIBUTING.md
|
||||
community/contributing/governance.md: https://github.com/knative/community/blob/main/GOVERNANCE.md
|
||||
community/contributing/mechanics.md: https://github.com/knative/community/tree/main/mechanics
|
||||
community/contributing/mechanics/creating-a-sandbox-repo.md: https://github.com/knative/community/blob/main/mechanics/CREATING-A-SANDBOX-REPO.md
|
||||
community/contributing/mechanics/creating-an-extensions-repo.md: https://github.com/knative/community/blob/main/mechanics/CREATING-AN-EXTENSIONS-REPO.md
|
||||
community/contributing/mechanics/feature-tracks.md: https://github.com/knative/community/blob/main/mechanics/FEATURE-TRACKS.md
|
||||
community/contributing/mechanics/golang-policy.md: https://github.com/knative/community/blob/main/mechanics/GOLANG-POLICY.md
|
||||
community/contributing/mechanics/release-schedule.md: https://github.com/knative/community/blob/main/mechanics/RELEASE-SCHEDULE.md
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ For the correct spellings of words, see [Merriam-Webster](https://www.merriam-we
|
|||
| Knative Eventing | eventing<br>Eventing Component | |
|
||||
| Knative Service<br>Service | Knative service<br>service<br>ksvc<br>svc | |
|
||||
| Knative Serving | serving<br>Serving Component | |
|
||||
|\`knative/docs\` GitHub repository | Knative Docs repo<br>Docs repo | This is true for every Knative repo, such as Sandbox, etc. |
|
||||
|\`knative/docs\` GitHub repository | Knative Docs repo<br>Docs repo | This is true for every Knative repo, such as Extensions, etc. |
|
||||
| Kubernetes | kubernetes | |
|
||||
| later | below | Don't use directional language to refer to a position in a document. |
|
||||
| might | may | Reserve "may" for official policy or legal considerations. To convey possibility, use "can" or "might". To convey permission, use "can". |
|
||||
|
|
|
|||
|
|
@ -15,9 +15,9 @@ An event source plugin has the following characteristics:
|
|||
|
||||
## List of Knative plugins
|
||||
|
||||
You can view all available `kn` plugins in the [Knative Sandbox repository](https://github.com/orgs/knative-extensions/repositories?q=kn+plugin&type=all&language=&sort=).
|
||||
You can view all available `kn` plugins in the [Knative Extensions repository](https://github.com/orgs/knative-extensions/repositories?q=kn+plugin&type=all&language=&sort=).
|
||||
|
||||
<!--TODO: If we're including the following table, the Client WG must be responsible for ensuring that the table is kept up to date, otherwise it should be removed from the docs and just the link to the sandbox repo should be provided-->
|
||||
<!--TODO: If we're including the following table, the Client WG must be responsible for ensuring that the table is kept up to date, otherwise it should be removed from the docs and just the link to the extensions repo should be provided-->
|
||||
|
||||
| Plugin | Description | Available via Homebrew? |
|
||||
| --- | --- | :---: |
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ election process for our technical oversight committee.
|
|||
- [Repository Guidelines](https://github.com/knative/community/blob/main/REPOSITORY-GUIDELINES.md):
|
||||
how we create and remove core repositories.
|
||||
|
||||
- [Sandbox repo process](https://github.com/knative/community/blob/main/mechanics/CREATING-A-SANDBOX-REPO.md):
|
||||
- [Extensions repo process](https://github.com/knative/community/blob/main/mechanics/CREATING-AN-EXTENSIONS-REPO.md):
|
||||
how to create a repo in the [`knative-extensions`](https://github.com/knative-extensions) GitHub org.
|
||||
|
||||
- [Feature tracks](https://github.com/knative/community/blob/main/mechanics/FEATURE-TRACKS.md):
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ This type of integration requires more effort than using some simpler integratio
|
|||
!!! note
|
||||
If you have created a new event source type that is not a part of the core Knative project, you can open a pull request to add it to the list of [Third-Party Sources](../../sources/#third-party-sources), and announce the new source in the [#knative-eventing Slack channel](https://cloud-native.slack.com/archives/C04LMU33V1S).
|
||||
|
||||
You can also add your event source to the [`knative-extensions`](https://github.com/knative-extensions) organization, by following the instructions to [create a sandbox repository](https://github.com/knative/community/blob/main/mechanics/CREATING-A-SANDBOX-REPO.md).
|
||||
You can also add your event source to the [`knative-extensions`](https://github.com/knative-extensions) organization, by following the instructions to [create a extensions repository](https://github.com/knative/community/blob/main/mechanics/CREATING-AN-EXTENSIONS-REPO.md).
|
||||
|
||||
## Required components
|
||||
|
||||
|
|
|
|||
|
|
@ -65,6 +65,6 @@ spec:
|
|||
implementations, such as Channels or Sources, actually implement support
|
||||
for the field. The shared `HTTPMessageSender.SendWithRetries()` logic has
|
||||
been enhanced to support this feature, and all implementations using it to
|
||||
perform retries will automatically benefit. Sandbox implementations not
|
||||
perform retries will automatically benefit. Extensions implementations not
|
||||
based on this shared library, for example RabbitMQ or Google Pub/Sub, would
|
||||
require additional development effort to respect the `retryAfterMax` field.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ For more information see the [language pack](https://github.com/knative/func/blo
|
|||
## Using external Git repositories
|
||||
|
||||
When creating a new function, a Git repository can be specified as the source
|
||||
for the template files. The Knative Sandbox maintains a set of [example templates](https://github.com/knative-extensions/func-tastic){target=_blank} which can be used during project creation.
|
||||
for the template files. The Knative Extensions maintains a set of [example templates](https://github.com/knative-extensions/func-tastic){target=_blank} which can be used during project creation.
|
||||
|
||||
For example, you can run the following command to use the [`metacontroller`](https://metacontroller.github.io/metacontroller/){target=_blank} template for Node.js:
|
||||
|
||||
|
|
@ -19,13 +19,13 @@ func create myfunc -l nodejs -t metacontroller --repository https://github.com/k
|
|||
|
||||
Language packs can be installed locally by using the [`func repository`](https://github.com/knative/func/blob/main/docs/reference/func_repository.md){target=_blank} command.
|
||||
|
||||
For example, to add the Knative Sandbox example templates, you can run the following command:
|
||||
For example, to add the Knative Extensions example templates, you can run the following command:
|
||||
|
||||
```{ .console }
|
||||
func repository add knative https://github.com/knative-extensions/func-tastic
|
||||
```
|
||||
|
||||
After the Knative Sandbox example templates are installed, you can use the `metacontroller` template by specifying the `knative` prefix in the `create` command:
|
||||
After the Knative Extensions example templates are installed, you can use the `metacontroller` template by specifying the `knative` prefix in the `create` command:
|
||||
|
||||
```{ .console }
|
||||
func create -t knative/metacontroller -l nodejs my-controller-function
|
||||
|
|
|
|||
Loading…
Reference in New Issue