-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
gp env to respect workspace env vars #16414
Conversation
started the job as gitpod-build-ak-gp-env-project.2 because the annotations in the pull request description changed |
7c5cd41
to
4c51d0e
Compare
4c51d0e
to
cdc0cdb
Compare
cdc0cdb
to
96d2dc4
Compare
96d2dc4
to
f9aa0c9
Compare
@svenefftinge @geropl I have not tested yet, going after the lunch, but I've refactored it that now there is |
f9aa0c9
to
4ab4dd3
Compare
/werft run with-clean-slate-deployment=true recreate-vm=true 👍 started the job as gitpod-build-ak-gp-env-project.10 |
4ab4dd3
to
29972d3
Compare
9cc5607
to
eac186c
Compare
const res = new Map<string, string>(); | ||
const imageAuth = projectEnvVars.find((e) => e.name === "GITPOD_IMAGE_AUTH"); | ||
const imageAuth = envVars.project.find((e) => e.name === "GITPOD_IMAGE_AUTH"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@svenefftinge this is the major reason why we need to return all, although we could change that this method itself fetches a required env var.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why this env var needs to be set on project-level and not anyhow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@svenefftinge I removed other layers, but kept this one for now. I think someone else can address it later if needed. Looking at the original PR and docs it seems to be that intent was to allow it only on project env vars.
/werft run 👍 started the job as gitpod-build-ak-gp-env-project.15 |
417596d
to
dab9381
Compare
dab9381
to
038e199
Compare
038e199
to
f7a655f
Compare
/werft run 👍 started the job as gitpod-build-ak-gp-env-project.19 |
/hold just want @geropl to double check, can someone from @gitpod-io/engineering-ide to review 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/unhold |
Description
gp env
reflects workspace env vars, not only user env vars, i.e. as well coming from projects and context URL.Related Issue(s)
fix #12208
How to test
gp env
reflects visible project and context env vars.Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-test
Publish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh