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

sample "bot-proactive-messaging-teamsfx" need update bicepCliVersion to 0.9.1 #1529

Open
ayachensiyuan opened this issue Jan 16, 2025 · 3 comments
Assignees

Comments

@ayachensiyuan
Copy link

Since ubuntu v24 cannot support libssl1.1, there will be an error when provision using bicepcliversion 0.4.613 runs on ubuntu v24 , and it need to upgrade to 0.9.1.

Image Image
@sayali-MSFT
Copy link
Collaborator

sayali-MSFT commented Jan 16, 2025

@ayachensiyuan - Thank you for your inquiry about your Teams app development issue!
We will inform the sample team, and they will update the sample accordingly.

@Mohammed-MSFT
Copy link
Contributor

Mohammed-MSFT commented Jan 17, 2025

Hi @ayachensiyuan - Thank you for your inquiry about your Teams app development issue!
We have upgraded to the version you suggested and tested it. It is working fine. Thank you for your input!

Image

Working ScreenShot

Image

@ayachensiyuan
Copy link
Author

Image In a certain scenario, there will be a problem with writing this way. If the user clones the sample directly, leaving the value empty will cause an error prompt in the yaml file. Since teams toolkit extension will automatically generate the key and value when creating or provisioning, the recommended way is to delete the key directly. I believe this key value was accidentally brought in, and the best way is to delete it directly. Because the yaml file of other teams toolkit projects does not contain this key either. @Mohammed-MSFT you can test it if delete this still work when provision and it will recreate new one.

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

No branches or pull requests

3 participants