-
Notifications
You must be signed in to change notification settings - Fork 167
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
[Issue] package
hooks order
#3855
Comments
The |
@justinyoo have you take a look at customizable azd up workflow. |
@rajeshkamal5050 Thanks for the link! I found it a few days back and applied it to mine. |
Hi @justinyoo. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “ |
Hi @justinyoo, since you haven’t asked that we “ |
Output from
azd version
pwsh> azd version azd version 1.8.2 (commit 14600c7a54edac4f54397413f8638431f5c16327)
Describe the bug
Currently, both
prepackage
andpostpackage
hooks are run after theup
hook and before the provisioning step.Can we run both
package
hooks after thepostprovision
hook and before thepredeploy
hook so that we can apply results to the deployment step, which are taken from the provisioning?Here's an example:
I'd like to get a URL of a provisioned resource and update a
config.json
of a frontend app to be deployed to Static Web App. It's not possible to updateconfig.json
because theprepackage
hook occurs before the provisioning step.As a workaround, I have to run the
predeploy
hook script to update theconfig.json
file.As long as it's a plain JSON file, it's OK. However, if we need to compile binaries, the package hooks should be run in between provisioning and deployment instead of before provisioning, which makes more sense to me.
To Reproduce
N/A
Expected behavior
I was expecting that the package step would occur after the provisioning. However, it actually occurred before the provisioning.
Environment
Information on your environment:
The text was updated successfully, but these errors were encountered: