-
Notifications
You must be signed in to change notification settings - Fork 126
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
Creating types sequentially takes a long time #524
Comments
What typically is done to run type-registration in parallel is to increase the this will ensure the types gets registered to different accounts & regions in parallel. hope that helps |
Thanks — I have I don't have it on for the Types:
Type: include
+ MacConcurrentTasks: 100
DependsOn: OrganizationBuild
Path: ./templates/005-types/_tasks.yml Where would be the best place to document this (so I can close the issue — assuming it does in fact work)? |
for documentation on this attribute I would refer to the documentation on the include-task. It already mentions the attribute. If you would have expected it somewhere else: feel free to add it! also happy to close the issue as-is. thanks |
org-formation-cli/src/plugin/impl/rp-build-task-plugin.ts
Lines 127 to 130 in 416dbaa
Is there a way to execute this for multiple types in parallel, so the total wait time is roughly a minute, the time it appears to take for the type to register, as opposed to n minutes for n types — this feels unnecessarily painful when setting up new accounts, in an existing organization (if it only happened when setting up the org then I'd be ok with it, though it would not be ideal)?
Naively, I might expect that rewriting the plugin to handle multiple types would then work… but I don't know whether there are AWS limits. If there is no such limit, would such a change — or an equivalent — be welcome? (I'd add a new plugin, to avoid breaking changes.)
The text was updated successfully, but these errors were encountered: