This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 789db7932f23483ec783a588d2b90700c2a8f71b
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Wed Apr 21 08:08:42 2021 +0200
Moving from master branch to main
---
proposals/provided-kamelets.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/proposals/provided-kamelets.adoc b/proposals/provided-kamelets.adoc
index a3af111..96c4994 100644
--- a/proposals/provided-kamelets.adoc
+++ b/proposals/provided-kamelets.adoc
@@ -50,7 +50,7 @@ As we move forward, we may want to build together a Catalog
of curated Kamelets
There's a procedure to embed Kamelets in the operator, but it's not used.
The current implementation currently looks up Kamelets in the current
namespace first, then in the operator namespace (in case it's different), then
-it does a lookup on the `master` branch in
https://github.com/apache/camel-kamelets to search for a specific Kamelet when
used.
+it does a lookup on the `main` branch in
https://github.com/apache/camel-kamelets to search for a specific Kamelet when
used.
This causes problems because it's not difficult to hit rate limiting on using
the Github APIs. There's a cache to avoid too many requests, but it's not
always sufficient.
== Proposal
