You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ts...@apache.org on 2021/04/27 08:21:30 UTC
[camel-k] branch main updated: chore(doc): fix doc syntax issues in
developers.adoc
This is an automated email from the ASF dual-hosted git repository.
tsato pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/main by this push:
new 4dcdaba chore(doc): fix doc syntax issues in developers.adoc
4dcdaba is described below
commit 4dcdaba95f154a24ff35e941df2db13dc3bb00ff
Author: Tadayoshi Sato <sa...@gmail.com>
AuthorDate: Tue Apr 27 17:19:48 2021 +0900
chore(doc): fix doc syntax issues in developers.adoc
---
docs/modules/ROOT/pages/contributing/developers.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributing/developers.adoc b/docs/modules/ROOT/pages/contributing/developers.adoc
index 47a6ecf..fa5c0ac 100644
--- a/docs/modules/ROOT/pages/contributing/developers.adoc
+++ b/docs/modules/ROOT/pages/contributing/developers.adoc
@@ -199,13 +199,13 @@ The build phase cannot be (currently) debugged in Minikube because the Kaniko bu
[publishing]
== Building Metadata for Publishing the Operator in Operator Hub
-----
Publishing to an operator hub requires creation and submission of metadata, required in a specific
https://github.com/operator-framework/operator-registry/#manifest-format[format]. The
https://sdk.operatorframework.io/docs/cli[operator-sdk] provides tools to help with the creation of this metadata.
There are two formats for the publishing of the metadata:
+
=== Package Manifests
The legacy packaging format used for deploying the operator to an OLM registry. While deprecated in Openshift 4.5+,
it is still supported and used on that and other cluster types. A single CSV is generated, comprising of the operator
@@ -216,8 +216,8 @@ To generate the metadata for camel-k in the legacy format, use the following com
make build-olm
----
The CSV and accompanying files are located in `deploy/olm-catalog`.
-**Note. these files are under version control.**
+NOTE: These files are under version control.
=== `bundles`
The latest packaging format used for deploying the operator to an OLM registry. This generates a CSV and related metadata