* Add DomainMapping docs
* x
* My oh my
* Add paragraph about wildcard (lack of) behaviour
* Update description and link to install docs
* Update link, use example.org domain, and elaborate contract for Ref
* update gen-api-reference-docs script
Updating the tool version to v0.3.0 tag.
Ran locally against v0.20.0 tag for serving/eventing repos, seems to be
working fine.
Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
* re-run api reference docs generation
Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
- Remove line with link about managed instio installation as that just links back to the install guide and doesn't provide any specific guidance.
- Improve readability
- remove duplicate statement in the wrong location
- reword incorrect statements
- reword statements to be consistent across the file
- fix incorrect statement referring to `Sequence` instead of `Trigger`
- replace `event-display` with `sequence-display` to match pod name
Signed-off-by: Sameer Vohra <vsameer@vmware.com>
* Adding configuration description for TLS/SASL for the KafkaChannel
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
* Updating based on feedback
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
* 💄 a little more context and polishing
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
* Fixing typo
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
- set weight to 70 so it shows as the last link in the list. This would
then match the intended order in the README.md file
Signed-off-by: Sameer Vohra <vsameer@vmware.com>
* Update .../sequence-termina/README.md
Relocate statement about Sequences to the correct section. It was hiding in the PingSource section ;p
* Update .../sequence-termina/README.md
Relocate statement about sequence container outputs in the "Inspecting results" section to the correct locations with their corresponding commands.
- Drop namespace reference in k8s Job resource as none of the other resources specify a namespace.
- Add verification for job having run
Signed-off-by: Sameer Vohra <vsameer@vmware.com>
Switch `service` to `resources` when referring to internal Knative Eventing.
Why: Disambiguate `service` to refer to an abstraction which has an http endpoint and primarily referring to a K8s Service or Knative Service.
Here, also calling Knative Eventing resources as `services` creates confusion even if the usage is technically correct.
Remove the relative link that links directly to the section above. It also goes to the generic install instructions rather than Eventing specifically.
Signed-off-by: Sameer Vohra <vohra.sam@gmail.com>
* fix: add a reference to eventing sources page instead of having a list
* docs: improve eventing sources readability
Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
* fix: use relative path for reference
* fix: use correct link for knative event sources
Co-authored-by: RichieEscarez <rescarez@google.com>
Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
Co-authored-by: RichieEscarez <rescarez@google.com>
Izabela Gomes
Julian Friedman
Carlos Santana
Ahmet Alp Balkan
Victor Agababov
Jean-Rémy Bancel
Kenjiro Nakayama
zhaojizhuang
knative-automation
Ashleigh Brennan
Sameer Vohra
dependabot[bot]
RichieEscarez
Matthias Wessendorf
Evan Anderson
Ville Aikas
Senthilnathan M
Vincent
Lukas Berk
Ricardo Zanini
SaintMalik
Dan Wilson
Zhuang
zhihuiwu
Alex Yang
Aldo Preciado Cuevas