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

Override the build command in the appsvc.yaml file #2241

Open
reissbaker opened this issue Nov 5, 2023 · 0 comments
Open

Override the build command in the appsvc.yaml file #2241

reissbaker opened this issue Nov 5, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@reissbaker
Copy link

reissbaker commented Nov 5, 2023

Feature Request

Hello! Since I have different build commands for dev vs production in my Node.js app, I want to be able to override the build command used for production. Currently I do this with the CUSTOM_BUILD_COMMAND env var (stored as an Application Setting in Azure App Service). However, this is pretty suboptimal:

  • If I want to iterate or change the build process for production, since the build command is stored solely in an environment variable, there's no simple way to revert a bad change: once I overwrite the env var in Application Settings, the previous value is gone. If it were tracked in git, it would be easy to revert a bad change.
  • I can't use ordinary code review tools like Github PRs to track and approve changes.
  • Existing access control and audit logs for code changes can't be reused.

I notice that the appsvc.yaml file allows overriding the pre-build, post-build, and run steps. This is almost exactly what I need! But it doesn't allow overriding the actual build: I tried adding a build section to the YAML file, since it appears that the C# code to at least read the build key exists, but... It didn't do anything, and Oryx continued to use the built-in build command, ignoring my build step from the appsvc.yaml file.

It would be amazing if I could override the build command using appsvc.yaml — it would be much preferable to using an environment variable. I would love to be able to manage all elements of building and running the app via configuration files stored in my repo, rather than environment variables and custom app settings in Azure App Service.

@simonjj simonjj added the enhancement New feature or request label Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants