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

Alllow port to be set via env instead hardcoded #869

Merged
merged 2 commits into from May 15, 2024

Conversation

RRap0so
Copy link
Contributor

@RRap0so RRap0so commented May 10, 2024

TL;DR

This allows port to be set via env variable and if not set uses default 8080.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Complete description

How did you fix the bug, make the feature etc. Link to any design docs etc
Created an environment variable and use it in the startup code. I've tested this by building a image locally with the env set with a port 9999 and without.

Tracking Issue

fixes flyteorg/flyte#5347

Signed-off-by: Rafael Raposo <rafaelraposo@spotify.com>
@RRap0so RRap0so changed the title Prefer env port instead hardcoded Alllow port to be set via env instead hardcoded May 10, 2024
@eapolinario eapolinario merged commit bb1db21 into flyteorg:master May 15, 2024
10 checks passed
@flyte-bot
Copy link
Collaborator

🎉 This PR is included in version 1.12.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants