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

Introduce --https flag which will add option to run all e2e tests with different http and https settings #1520

Open
mvinkler opened this issue Nov 12, 2021 · 7 comments
Labels
good first issue Denotes an issue ready for a new contributor. kind/feature New feature or request triage/accepted Issues which should be fixed (post-triage)

Comments

@mvinkler
Copy link
Contributor

mvinkler commented Nov 12, 2021

Feature request

Please introduce --https flag, similar to one in knative/serving: knative/serving#5157

Use case

The flag will add option to run all e2e tests with different http and https settings.
Currently, TestDomain test expects the first service to be available at http, and the second at https, but this may not be the case if "defaultExternalScheme" is set to https.

@mvinkler mvinkler added the kind/feature New feature or request label Nov 12, 2021
@rhuss rhuss added the triage/accepted Issues which should be fixed (post-triage) label Nov 17, 2021
@rhuss rhuss moved this to Icebox in Client Planning Jan 25, 2022
@rhuss rhuss added the good first issue Denotes an issue ready for a new contributor. label Jan 25, 2022
@JuneOh710
Copy link

/assign

@briheet
Copy link

briheet commented Dec 23, 2023

Hey @rhuss , if @JuneOh710 is not working on this issue, i would like to work on it as it interests me. Could you brief me a little about this ? I did look into feature request and the use case, could you touch on things where should i start with ?

@JuneOh710
Copy link

Hey @rhuss , if @JuneOh710 is not working on this issue, i would like to work on it as it interests me. Could you brief me a little about this ? I did look into feature request and the use case, could you touch on things where should i start with ?

Hello, @briheet01. I took on this issue as a part of an initiative for undergrad students. I'm actually meeting with a member of knative today at 5pm EST to discuss this issue. Would it be possible for you to let us continue working on this issue?

@briheet
Copy link

briheet commented Dec 23, 2023

@JuneOh710 Yeah sure, good luck.

@JuneOh710 JuneOh710 removed their assignment May 5, 2024
@asr2003
Copy link

asr2003 commented Jun 1, 2024

@aliok Is this issue is ready to grab? I would like to explore the projects of our Knative community.

@mabulgu
Copy link

mabulgu commented Jun 21, 2024

I want to work on this issue if no one is working on it yet. I am assigning it to myself but pls do unassign me if you have sbd else working on this one already.
Note that my contributions might take time and if I am assigned to an issue this means I am genuinely working on it.

/assign

@mabulgu mabulgu removed their assignment Aug 26, 2024
@mabulgu
Copy link

mabulgu commented Aug 26, 2024

Sorry I needed to unassign this from myself as I could not find much time to work on this as I am going thru a difficult pace on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor. kind/feature New feature or request triage/accepted Issues which should be fixed (post-triage)
Projects
Status: Backlog
Development

No branches or pull requests

6 participants