-
Notifications
You must be signed in to change notification settings - Fork 33
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
add sha and version to ‘/‘ endpoint #574
Conversation
let version | ||
let sha | ||
function setup(buildsha, appVersion) { | ||
version = appVersion | ||
sha = buildsha | ||
return router | ||
} |
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.
This works but I'm not sure how well I like keeping the values as global state in this file. Couldn't we just access the config directly here instead of passing as variables?
Additionally, I'm wondering if it'd be worth to still escape these values, even though they should usually be under our control.
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.
The style matches that used in other endpoints. I'm open to other options.
13cf5c3
to
ce50ee8
Compare
@@ -23,7 +23,7 @@ jobs: | |||
build-and-deploy: | |||
name: Build and Deploy | |||
needs: upload-package-lock-json | |||
uses: clearlydefined/operations/.github/workflows/app-build-and-deploy.yml@v2.0.0 | |||
uses: clearlydefined/operations/.github/workflows/app-build-and-deploy.yml@0a6c2607470e2e0e49bf2d6636223bcd62c1a7f8 |
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.
Needs to be changed once operations PR merged
APP_VERSION replaces it
Description
Add configurations for
BUILD_SHA
andAPP_VERSION
to use for debugging.Related Work
Unresolved
The deploy isn't happening through the reusable workflows that would set these configs. Additionally, it is not clear how deploys are happening in the current Azure DevOps deploy. Some investigation is needed before merging.