mirror of https://github.com/pulumi/pulumi.git
9388c54be7
<!--- Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation. --> # Description Originally motivated by uncontrolled pseudo-recurcive type expansion in AWS WafV2, we've limited the number of types that we should in the docs to 200: https://github.com/pulumi/pulumi/pull/12070 Our large customer that publishes their own packages and docs came back to us and said they have legitimate use cases with more than 200 types: #15507 I've grabbed stats about our current packages and still found a few offenders: ``` "aws:lex/v2modelsIntent:V2modelsIntent" 920 "aws:wafv2/ruleGroup:RuleGroup" 310 "aws:wafv2/webAcl:WebAcl" 523 "azure-native:datafactory:Dataset" 256 "azure-native:datafactory:LinkedService" 299 "azure-native:datafactory:Pipeline" 618 "azure-native:datamigration:ServiceTask" 291 "azure-native:datamigration:Task" 291 "aws-native:quicksight:Analysis" 589 "aws-native:quicksight:Dashboard" 606 "aws-native:quicksight:Template" 590 ``` Therefore, I'm not entirely removing the limit in this PR, but a) bumping the default to 1000 b) applying 200 to the known offenders only I don't love it's hard coded, but I haven't found a place to add simple configuration nob. Anyway, it's slightly less hard-coded than it used to be. Fixes #15507 ## Checklist - [x] I have run `make tidy` to update any new dependencies - [x] I have run `make lint` to verify my code passes the lint check - [ ] I have formatted my code using `gofumpt` <!--- Please provide details if the checkbox below is to be left unchecked. --> - [x] I have added tests that prove my fix is effective or that my feature works - Existing docs gen tests cover that I haven't broken anything - I re-generated the AWS docs and they had no changes <!--- User-facing changes require a CHANGELOG entry. --> - [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Cloud, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version <!-- @Pulumi employees: If yes, you must submit corresponding changes in the service repo. --> |
||
|---|---|---|
| .. | ||
| asset | ||
| authhelpers | ||
| backend | ||
| cmd/pulumi | ||
| codegen | ||
| display | ||
| engine | ||
| graph | ||
| importer | ||
| operations | ||
| resource | ||
| secrets | ||
| testing/integration | ||
| util | ||
| version | ||
| workspace | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
README.md
pulumi/pkg
While pulumi/sdk maintains strict backwards compatibility guarantees, code under pkg/ is handled more informally: while breaking changes are still discouraged they may happen when they make sense.