You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: azd package is currently a beta feature. This issue is created to capture the current design and remaining items.
Current
We've added a barebones azd package command, this has served two purposes:
Allow users to iterate locally by running azd package to ensure that the service projects can be built and packaged.
Allow users to have a better azd up experience. The local build will fail immediately before proceeding with Azure state changes.
Remaining items
Allow users to run azd package and examine the packaged outputs easily. An example of this perhaps is to not archive artifacts until we need to, since it's easier for users to not have to deal with unzipping archives.
Allow users to upload packaged artifacts in CD. Once again, archiving here may hinder the artifacts tooling ability to provide better UX experiences to examine files uploaded.
Ensure that azd deploy --from-package <pkg_folder> works correctly with these changes. Note that it should be possible for azd deploy --from-package to reject a folder that isn't packaged correctly (i.e., incorrect host, or not a valid understood azd artifact).
With the requirements above, we would need to package the service into a stable location. We would need to ensure that proper checks are in-place to retain idempotency requirements (clean + rebuild comes to mind, which is the current behavior when writing to temp).
Questions
How do artifacts like docker image show up with the proposed designs?
What would future artifacts look like? Do these designs work well with future considerations?
The text was updated successfully, but these errors were encountered:
One thing we possibly want to think about: Ideally, azd is designed with correct dependency management in-mind, and azd deploy --from-package would not require validation of a project folder amongst other things. See #1957
Moving this to Backlog. Since we have other big ticket items to handle. Any improvements to build/packaging areas can be handled based on users feedback/concerns.
Note:
azd package
is currently a beta feature. This issue is created to capture the current design and remaining items.Current
We've added a barebones
azd package
command, this has served two purposes:azd package
to ensure that the service projects can be built and packaged.azd up
experience. The local build will fail immediately before proceeding with Azure state changes.Remaining items
azd package
and examine the packaged outputs easily. An example of this perhaps is to not archive artifacts until we need to, since it's easier for users to not have to deal with unzipping archives.azd deploy --from-package <pkg_folder>
works correctly with these changes. Note that it should be possible forazd deploy --from-package
to reject a folder that isn't packaged correctly (i.e., incorrect host, or not a valid understood azd artifact).Questions
The text was updated successfully, but these errors were encountered: