This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch gcp-vault-1.10.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
discard 5054614a9 Regen
discard f0a5b03e8 Fix findings of validate job
discard 8f5764709 Added docs about GCP Secret Manager Vault Trait
discard 9c936179a Added some more information in the docs for GCP Secret
Manager Vault
discard 416f2afe5 Added Support GCP Secret Manager Vault from Camel
add 1eba50aa1 Added Support GCP Secret Manager Vault from Camel
add 8f52385b3 Added some more information in the docs for GCP Secret
Manager Vault
add 1b3cf1f0f Added docs about GCP Secret Manager Vault Trait
add 1ccbf3a43 Fix findings of validate job
add 10b252447 Regen
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (5054614a9)
\
N -- N -- N refs/heads/gcp-vault-1.10.x (10b252447)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
