[apisix-ingress-controller] branch dependabot/go_modules/test/e2e/github.com/gorilla/websocket-1.5.0 updated (9adc4f20 -> ec267010)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/go_modules/test/e2e/github.com/gorilla/websocket-1.5.0
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git


 discard 9adc4f20 chore(deps): bump github.com/gorilla/websocket in /test/e2e
     add aae2105e feat: ingress annotations support enable websocket (#1101)
     add 4d172a03 chore(deps): bump github.com/stretchr/testify in /test/e2e (#1113)
     add ec267010 chore(deps): bump github.com/gorilla/websocket in /test/e2e

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   (9adc4f20)
            \
             N -- N -- N   refs/heads/dependabot/go_modules/test/e2e/github.com/gorilla/websocket-1.5.0 (ec267010)

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:
 docs/en/latest/concepts/annotations.md  |  33 ++++
 pkg/kube/translation/ingress.go         |   8 +
 pkg/kube/translation/ingress_test.go    | 261 +++++++++++++++++++++++++++
 test/e2e/go.mod                         |   4 +-
 test/e2e/go.sum                         |   8 +-
 test/e2e/suite-annotations/websocket.go | 306 ++++++++++++++++++++++++++++++++
 6 files changed, 616 insertions(+), 4 deletions(-)
 create mode 100644 test/e2e/suite-annotations/websocket.go