-
Notifications
You must be signed in to change notification settings - Fork 199
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
docs: Updates to the upgrade summary doc #8704
base: dev
Are you sure you want to change the base?
docs: Updates to the upgrade summary doc #8704
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## dev #8704 +/- ##
=======================================
Coverage 78.96% 78.96%
=======================================
Files 608 608
Lines 41827 41827
Branches 8295 8295
=======================================
Hits 33030 33030
Misses 5460 5460
Partials 3337 3337 |
|
||
1. Created `teamsapp.yml` and `teamsapp.local.yml` in your project root folder. | ||
1. Created `teamsapp.yml` and `teamsapp.local.yml` in your projects root directory. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in your project's
root directory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in the new PR: #8710
* Configuration of the lifecycle management using Provision, Deploy, and Publish are now fully customizable and expressed in `teamsapp.local.yml` and `teamsapp.yml`. [More info](https://aka.ms/teamsfx-v5.0-guide#project-files) | ||
* Configuration and values that were saved in `.fx/config` and `.fx/state` are now handled with environment files and saved to `/env` by default. [More info](https://aka.ms/teams-toolkit-5.0-upgrade#environment-management) | ||
* The changes to use environment files give greater flexibility of configuring which resources are used to provision, but may require some manual steps when creating new environments. [More info](https://aka.ms/teams-toolkit-5.0-upgrade#environment-management) | ||
* Teams Toolkit no longer prompts you for which environment to use when using the Launch targets in `launch.json`. You can edit `.vscode/launch.json` and configure which environments are used. [More info](https://aka.ms/teams-toolkit-5.0-upgrade#launch-your-app) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed with @kuojianlu , this limitation no longer exists in V5 stable release. Teams Toolkit V5 will ask users select an env as usual. Can you help remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in the new PR: #8710
The base branch was changed.
@therealjohn I ported your changes to #8710 because this PR cannot be updated to merge to main branch directly. |
Adjusted the information in the upgrade summary.