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

Add Buildpack source to cloud support + Patch commands #6283

Merged
merged 106 commits into from
May 18, 2023
Merged

Add Buildpack source to cloud support + Patch commands #6283

merged 106 commits into from
May 18, 2023

Conversation

daniv-msft
Copy link
Contributor

Enable the local source to cloud + patching in Container Apps. Building and Patching is done using buildpack. Building is integrated with the Up command, and patching introduces three new CLI commands (cf. below).


This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az containerapp up
az containerapp patch list
az containerapp patch apply
az containerapp patch interactive

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
    => We have a couple of linting issues we're working on and will send an extra commit for soon, but given the short timeline we decided to send that as a second step.
  • Have you run python scripts/ci/test_index.py -q locally?

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

harryli0108 and others added 30 commits May 4, 2023 09:32
Use buildpacks for 'az containerapp up --source' no Dockerfile scenario
Fixed bug -- when multiple container apps are listed.
* Adding patch list

* Added patch list command

* Revert thumbprint arg

* Fix bugs

* Release ML 2.16.0 (#6259)

* Adds IoT Extension Release v0.21.2 (#6264)

* Integrated with Harry

* Use buildpacks for 'az containerapp up --source' no Dockerfile scenario

* Fixed bug

* Fixed command usage text

* Add warning when Docker client cannot be instantiated

---------

Co-authored-by: snehapar9 <snehapar@microsoft.com>
Co-authored-by: Neehar Duvvuri <40341266+needuv@users.noreply.github.com>
Co-authored-by: snehapar9 <108305436+snehapar9@users.noreply.github.com>
Co-authored-by: Ryan K <ryan.k@outlook.com>
Co-authored-by: daniv-msft <48293037+daniv-msft@users.noreply.github.com>
Co-authored-by: Cormac McCarthy <corm@microsoft.com>
- Handle failures caused during 'pack build' prerequisite checks
- Output 'pack build' result to stdout
- Pull pack CLI from GitHub release
* Adding patch list

* Added patch list command

* Revert thumbprint arg

* Fix bugs

* Integrated with Harry

* Fixed bug

* Fixed command usage text

* Made managed env optional

* Fixed identation

* Fixed identation

* Made env optional

* Remove patch list

---------

Co-authored-by: harrli <harrli@microsoft.com>
Co-authored-by: Harry Li <110055355+harryli0108@users.noreply.github.com>
@daniv-msft
Copy link
Contributor Author

@daniv-msft Please resolve the conflict

@zhoxing-ms Could you please clarify which conflict you're referring to? @snehapar9 resolved a merge conflict with the Workload Profile PR just today. Was it the one you were thinking about?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot ContainerApp
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants