Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change: [M3-7922] - Clear ACLB configuration certificates if http or tcp protocol is selected #10311

Conversation

bnussman-akamai
Copy link
Member

Description 📝

Updates the ACLB configuration to prevent users from running into an API error.

New API validation was added that will throw if you try to send certificates with a http or tcp configuration. We now need to make sure we don't send certificates if the user selects http or tcp for their configuration

How to test 🧪

Prerequisites

Reproduction steps

  • Without this PR checked out, you will observe that you can't change an HTTPS configuration to a HTTP or TCP. You would get an error saying Certificate table must be empty with configuration protocol "http"

Screenshot 2024-03-25 at 10 55 44 AM

Verification steps

  • Test creating/updating a configuration
    • Test with various different certificate / protocol combinations
    • Ensure the form works as expected

As an Author I have considered 🤔

  • 👀 Doing a self review
  • ❔ Our contribution guidelines
  • 🤏 Splitting feature into small PRs
  • ➕ Adding a changeset
  • 🧪 Providing/Improving test coverage
  • 🔐 Removing all sensitive information from the code and PR description
  • 🚩 Using a feature flag to protect the release
  • 👣 Providing comprehensive reproduction steps
  • 📑 Providing or updating our documentation
  • 🕛 Scheduling a pair reviewing session
  • 📱 Providing mobile support
  • ♿ Providing accessibility support

@bnussman-akamai bnussman-akamai added the ACLB Relating to the Akamai Cloud Load Balancer label Mar 25, 2024
@bnussman-akamai bnussman-akamai self-assigned this Mar 25, 2024
@bnussman-akamai bnussman-akamai requested a review from a team as a code owner March 25, 2024 14:58
@bnussman-akamai bnussman-akamai requested review from jdamore-linode and abailly-akamai and removed request for a team March 25, 2024 14:58
Copy link

github-actions bot commented Mar 25, 2024

Coverage Report:
Base Coverage: 81.65%
Current Coverage: 81.65%

@bnussman-akamai bnussman-akamai requested a review from a team as a code owner March 25, 2024 15:50
@bnussman-akamai bnussman-akamai requested review from cliu-akamai and removed request for a team March 25, 2024 15:50
Copy link
Contributor

@mjac0bs mjac0bs left a comment

Choose a reason for hiding this comment

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

This looked good from my testing with various cert(s) and protocol combinations. The e2e spec that errored passed locally + in CI and I observed the certificates array was cleared for both HTTP and TCP protocol, with successful PUT requests. Left one question about port # for TCP.

✅ HTTP
Screenshot 2024-03-25 at 9 41 23 AM

✅ TCP
Screenshot 2024-03-25 at 9 41 49 AM

// If the user has not manually changed the port, and they select HTTPS,
// set the port to 443 for them.
if (protocol === 'https') {
port = 443;
Copy link
Contributor

Choose a reason for hiding this comment

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

Is port 443 fine as a default for TCP protocol?
Screenshot 2024-03-25 at 9 50 06 AM

Copy link
Member Author

Choose a reason for hiding this comment

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

When this feature was added, they were okay with no default port for TCP. It will just use whatever was the existing value

@mjac0bs mjac0bs added the Add'tl Approval Needed Waiting on another approval! label Mar 25, 2024
Copy link
Contributor

@abailly-akamai abailly-akamai left a comment

Choose a reason for hiding this comment

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

Confirmed the before & after fix.

Was able to submit with all protocols ✅

Co-authored-by: Mariah Jacobs <114685994+mjac0bs@users.noreply.github.com>
@mjac0bs mjac0bs added Approved Multiple approvals and ready to merge! and removed Add'tl Approval Needed Waiting on another approval! labels Mar 25, 2024
@bnussman-akamai bnussman-akamai merged commit 488ff12 into linode:develop Mar 25, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ACLB Relating to the Akamai Cloud Load Balancer Approved Multiple approvals and ready to merge!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants