Stabilize service Helm unit tests for TLS-aware port naming

[Copilot]

The helm-test Actions job failed because service_test.yaml assumed spec.ports[0].name was always http, while chart behavior now renders https when useTLS is enabled. This PR makes the affected assertions explicit and deterministic.

• Problem alignment

  • The failure was isolated to charts/iap/tests/service_test.yaml assertions on port name.
  • Tests were implicitly inheriting TLS defaults from shared test values.

• Changes

  • Added useTLS: false to the specific service test cases that assert spec.ports[0].name: "http".
  • Scope is limited to test inputs; no template/runtime chart logic changed.

• Why this is the minimal fix

  • Preserves TLS-aware service behavior introduced in the chart.
  • Removes hidden coupling to shared defaults in test data.

# charts/iap/tests/service_test.yaml
set:
  service:
    name: "http-service"
    type: "ClusterIP"
    port: 80
  applicationPort: 80
  useTLS: false
  useWebSockets: false
asserts:
  - equal:
      path: spec.ports[0].name
      value: "http"

[Copilot]

Pull request overview

This PR aims to stabilize Helm unit tests for the charts/iap Service template by making TLS-related inputs explicit in test cases that assert a specific port name.

Changes:

• Adds useTLS: false to several service_test.yaml test cases to avoid inheriting TLS defaults from shared test values.
• Keeps assertions deterministic for tests that expect spec.ports[0].name: "http".

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.