Skip to content

[devstaging] Deploy all branches with HTTPS #2704

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

Closed
csweichel opened this issue Jan 8, 2021 · 0 comments · Fixed by #2853
Closed

[devstaging] Deploy all branches with HTTPS #2704

csweichel opened this issue Jan 8, 2021 · 0 comments · Fixed by #2853
Assignees
Labels
type: work item This issue pertains to something we have to do where the result is not code or a deployed feature
Milestone

Comments

@csweichel
Copy link
Contributor

At the moment one needs to add the https build config to get a branch that sports HTTPS support.
Now that we have higher lets encrypt quotas, we should make HTTPS the default in devstaging.

@csweichel csweichel added type: work item This issue pertains to something we have to do where the result is not code or a deployed feature roadmap item: registry facade labels Jan 8, 2021
@csweichel csweichel added this to the January 2021 milestone Jan 8, 2021
@csweichel csweichel self-assigned this Jan 8, 2021
csweichel pushed a commit that referenced this issue Jan 12, 2021
and remove the `https` build config. This is In preparation for making
registry-facade standard.

Fixes #2704
csweichel pushed a commit that referenced this issue Jan 14, 2021
and remove the `https` build config. This is In preparation for making
registry-facade standard.

Fixes #2704
pavan-tri pushed a commit to trilogy-group/gitpod that referenced this issue Apr 28, 2021
and remove the `https` build config. This is In preparation for making
registry-facade standard.

Fixes gitpod-io#2704
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: work item This issue pertains to something we have to do where the result is not code or a deployed feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant