You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: generator/README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,11 +32,15 @@ View the Pipeline Configuration [here](/azure-pipelines-autogen.yml).
32
32
3. If there are any modifications to [schemas/common/autogeneratedResources.json](/schemas/common/autogeneratedResources.json), push a commit to the autogenerate branch to make any corresponding changes to [schemas/2014-04-01-preview/deploymentTemplate.json](/schemas/2014-04-01-preview/deploymentTemplate.json) and [schemas/2015-01-01/deploymentTemplate.json](/schemas/2015-01-01/deploymentTemplate.json).
33
33
34
34
#### Onboarding to the autogeneration pipeline
35
-
36
-
1. Follow the steps listed under [Getting Started](#getting-started). The following commands assume you are running in the `generator` directory.
37
-
3. Run `npm run list-basepaths` to discover the specs repo path containing the swagger definitions.
38
-
4. Run `npm run generate-single {basePath}` to generate schemas for them. Save the console output to file.
39
-
5. Manually remove any existing references to your provider namespace (if any) from [schemas/2019-04-01/deploymentTemplate.json](/schemas/2019-04-01/deploymentTemplate.json).
40
-
6. Add the {basePath} to the autogenlist array in [autogenlist.ts](./autogenlist.ts).
41
-
7. Commit all the changed files, and submit a PR to this repo with title "Onboarding {provider} for autogeneration". Include the full output saved in step 2 as a comment.
42
-
8. Ensure all CI tests pass, and ask the team to review the PR (including tool output) to ensure that all expected resources have been detected and generated as expected.
35
+
New resource providers are onboarded for autogeneration by default, so the only providers which have been opted out are listed in [autogenlist.ts](./autogenlist.ts) with `disabledForAutogen` set.
36
+
37
+
If your team has been opted out, and you would like to opt in, please raise an issue in this repo, and we will assist.
38
+
39
+
> The following steps are no longer necessary for onboarding, but listed here for reference:
40
+
> 1. Follow the steps listed under [Getting Started](#getting-started). The following commands assume you are running in the > `generator` directory.
41
+
> 3. Run `npm run list-basepaths` to discover the specs repo path containing the swagger definitions.
42
+
> 4. Run `npm run generate-single {basePath}` to generate schemas for them. Save the console output to file.
43
+
> 5. Manually remove any existing references to your provider namespace (if any) from [schemas/2019-04-01/deploymentTemplate.> json](/schemas/2019-04-01/deploymentTemplate.json).
44
+
> 6. Add the {basePath} to the autogenlist array in [autogenlist.ts](./autogenlist.ts).
45
+
> 7. Commit all the changed files, and submit a PR to this repo with title "Onboarding {provider} for autogeneration". Include > the full output saved in step 2 as a comment.
46
+
> 8. Ensure all CI tests pass, and ask the team to review the PR (including tool output) to ensure that all expected resources > have been detected and generated as expected.
// Disabled as the swagger spec contains a type ("DateTimeRfc1123") which autorest is unable to parse: https://github.com/Azure/autorest.azureresourceschema/issues/71
0 commit comments