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

Use parameter --manifest-file-path / --manifest-path #10251

Closed
jchomarat opened this issue Oct 31, 2023 · 5 comments
Closed

Use parameter --manifest-file-path / --manifest-path #10251

jchomarat opened this issue Oct 31, 2023 · 5 comments
Assignees
Labels

Comments

@jchomarat
Copy link

Describe the bug
I am trying to run the following command

teamsfx package --env prod --manifest-path "path-to-manifest"

Then I got the the message asking me to select a manifest.

image

Looking at the doc the parameter is supposed to be --manifest-file-path but this one in unrecognized.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. 22]

CLI Information (please complete the following information):

  • OS: [e.g. iOS8.1]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@jayzhang
Copy link
Member

jayzhang commented Nov 1, 2023

@jchomarat Thanks for reporting the issue. Actually, the doc is out of date. Please use teams-manifest-file instead:
image

@jchomarat
Copy link
Author

jchomarat commented Nov 2, 2023

@jayzhang, which version are you using. Here is what I have

image

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Nov 2, 2023
@jayzhang
Copy link
Member

jayzhang commented Nov 7, 2023

@jchomarat Sorry for misunderstanding. In version 2.0.2, the default mode is interactive, if you want to run the command in none-interactive mode, please add an option: --interactive false for this command.

@jchomarat
Copy link
Author

hey @jayzhang - oh ok, makes sense even though it was not clear. Thanks, works like a charm

@adashen adashen removed the needs attention This issue needs the attention of a contributor. label Nov 8, 2023
@adashen
Copy link
Contributor

adashen commented Nov 8, 2023

Close as the issue is resolved

@adashen adashen closed this as completed Nov 8, 2023
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