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

doc for mtad-gen option in module build #724

Merged
merged 3 commits into from
Apr 7, 2020
Merged

doc for mtad-gen option in module build #724

merged 3 commits into from
Apr 7, 2020

Conversation

katunin-ng
Copy link
Member

Before submitting a pull request, please ensure the following:

Description

Please explain the changes you made.

Add a link to the design (if applicable).

Checklist

  • Code compiles correctly
  • Relevant tests were added (unit / contract / integration)
  • Relevant logs were added
  • Formatting and linting run locally successfully
  • All tests pass
  • UA review
  • Design is documented
  • Extended the README / documentation, if necessary
  • Open source is approved

@katunin-ng katunin-ng requested a review from ShimiT as a code owner April 7, 2020 08:38
| `-e (--extensions)` | Optional | The path or paths to multitarget application extension files (`.mtaext`). Several extension files separated by commas can be passed with a single flag, or each extension file can be specified with its own flag.| `mbt module-build -m=my_module -e=test1.mtaext,test2.mtaext`<br>or<br>`mbt module-build -m=my_module -e=test1.mtaext -e=test2.mtaext`
| `-g (--mtad-gen)` | Optional | If the parameter is provided, the deployment descriptor `mtad.yaml` is generated by default in the current folder or in the folder configured by the `--target` parameter. <br> A module's `path` property in the generated `mtad.yaml` file points to the module's build results if this module was selected using the `--modules` option. <br><br> <b>Notes</b>:<ul><li>The selected module list specified using the `--module` option, does not affect the list of modules in the resulting `mtad.yaml` file. The `mtad.yaml` file is always generated according to the default Cloud MTA Builder settings, the `build-parameters` configurations in the `mta.yaml` file (e.g. `supported-platforms`), and the selected target platform.<li>By default, the `mtad.yaml` is generated for the `cf` target platform. You can configure a different target plaform using the `--platform` option. | `mbt module-build -m=my_module1, my_module2 –g`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mbt module-build -m=my_module1, my_module2 –g
please care to remove space between modules or put them with own -m flag or with ""

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link
Contributor

@tal-sapan tal-sapan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change to - in the examples

@tal-sapan tal-sapan merged commit 7d8628d into master Apr 7, 2020
@delete-merged-branch delete-merged-branch bot deleted the docmtadgen branch April 7, 2020 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants