Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Jun 13, 2025

What type of PR is this?

Bug

Which issue does this PR fix:
#733

What does this PR do / Why do we need it:
This corrects failing access log subscription tests that were previously disabled. The impacted assertions are safe to remove as the following assertions that check for the existence/non-existence of the subscriptions are enough to confirm a success. I also manually verified through the AWS console.

If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
N/A

Testing done on this change:

export FOCUS="Access Log Policy" && make e2e-test

...

[SynchronizedAfterSuite] PASSED [31.076 seconds]
------------------------------

Ran 13 of 72 Specs in 500.998 seconds
SUCCESS! -- 13 Passed | 0 Failed | 0 Pending | 59 Skipped
--- PASS: TestIntegration (501.00s)
PASS
ok      github.com/aws/aws-application-networking-k8s/test/suites/integration   501.775s

Automation added to e2e:

N/A

Will this PR introduce any new dependencies?:

No.

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No.

Does this PR introduce any user-facing change?:

No.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ghost ghost added the bug Something isn't working label Jun 13, 2025
@ghost ghost self-assigned this Jun 13, 2025
@ghost ghost enabled auto-merge June 13, 2025 21:59
}
alp := &anv1alpha1.AccessLogPolicy{}
err := testFramework.Client.Get(ctx, alpNamespacedName, alp)
g.Expect(err).To(BeNil())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason to remove these asserts?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opted to remove them in favour of the asserts following. The later asserts could not pass if these access log polices were not created anyways.

Copy link
Contributor

@mikestvz mikestvz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ LGTM

@ghost ghost added this pull request to the merge queue Jun 13, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jun 14, 2025
@ghost ghost enabled auto-merge June 14, 2025 01:28
@ghost ghost added this pull request to the merge queue Jun 14, 2025
Merged via the queue into aws:main with commit e8eebc5 Jun 14, 2025
2 checks passed
@ghost ghost deleted the test/correct-access-logs branch June 16, 2025 16:55
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant