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

Finalize azd package design #2079

Open
weikanglim opened this issue May 2, 2023 · 4 comments
Open

Finalize azd package design #2079

weikanglim opened this issue May 2, 2023 · 4 comments
Labels
Milestone

Comments

@weikanglim
Copy link
Contributor

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:

  1. Allow users to iterate locally by running azd package to ensure that the service projects can be built and packaged.
  2. Allow users to have a better azd up experience. The local build will fail immediately before proceeding with Azure state changes.

Remaining items

  1. 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.
  2. 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.
  3. 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).
  4. 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

  1. How do artifacts like docker image show up with the proposed designs?
  2. What would future artifacts look like? Do these designs work well with future considerations?
@weikanglim weikanglim added this to the Backlog milestone May 2, 2023
@weikanglim weikanglim changed the title Finalize azd package for official release Finalize azd package design May 2, 2023
@weikanglim
Copy link
Contributor Author

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

@savannahostrowski savannahostrowski modified the milestones: Backlog, Gallium May 8, 2023
@savannahostrowski
Copy link
Contributor

@rajeshkamal5050 Not sure that we are going to get to this in Gallium. Should we move to Germanium? Backlog?

@rajeshkamal5050
Copy link

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.

@savannahostrowski
Copy link
Contributor

Consider #1698 and #1810 via azd package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants