This is an automated email from the ASF dual-hosted git repository.
vishesh92 pushed a change to branch feat-add-stickyness-policy
in repository
https://gitbox.apache.org/repos/asf/cloudstack-kubernetes-provider.git
omit 207f378d Feat: Add support for stickyness policy
add 6be16ff0 add some unit tests
add c93aee96 Apply suggestion from @Copilot
add 43bde74d add some unit tests (#90)
add 4740dbca Release v1.2.0 (#91)
add 6ba72061 Add .asf.yaml (#98)
add 0fdca7b6 Add security-model discoverability pointer to the
project-wide CloudStack threat model (#97)
add a7723fb5 Feat: Add support for stickyness policy
add 6b74579e Update cloudstack-go
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 (207f378d)
\
N -- N -- N refs/heads/feat-add-stickyness-policy (6b74579e)
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:
.github/workflows/golangci-lint.yml => .asf.yaml | 39 +-
AGENTS.md | 13 +
README.md | 84 +-
SECURITY.md | 35 +
cloudstack_instances_test.go | 75 +
cloudstack_loadbalancer_test.go | 2921 ++++++++++++++++++++++
cloudstack_test.go | 40 +
deployment.yaml | 2 +-
go.mod | 4 +-
go.sum | 4 +-
10 files changed, 3190 insertions(+), 27 deletions(-)
copy .github/workflows/golangci-lint.yml => .asf.yaml (67%)
create mode 100644 AGENTS.md
create mode 100644 SECURITY.md
