No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

first at least drop the suffix `Args` if possible because it's not consistent with docs

Then make use of namespaces as Zen of python says - I wonder how it would look if we could break it down into packages
```import this
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.```
Let's say:
I have `ServiceSourceConfiguration`

Found another one with 84! :smile:
ServiceSourceConfigurationCodeRepositoryCodeConfigurationCodeConfigurationValuesArgs

FWIW, you don’t need to use the `Args` classes. They are provided as a convenience and an alternative to using keyword args. We added them recently as a user request so that args could be passed around separately from the resources.

That being said, this is not about python but how the resources are structured in the encapsulating providers. Anyway, welcome to our world… let us know if you figure out how to do it in a way that you find more appealing and we’ll consider it :slightly_smiling_face:

I took a lot of inspiration from CDK to me it seems they are on the right track

Instead of this
```authentication_configuration={
            "connection_arn": aws_apprunner_connection["example"]["arn"],
        }```
I'd rather
```authentication_configuration=AuthenticationConfiguration(connection_arn='asdf')```
In case this would be a conflict then use namespace -&gt; sub-package

then user has choice whether to use full name from the parent
or import as deeply as needed

eg.
```from pulumi_aws.apprunner.service import AuthenticationConfiguration```


&gt; I’d rather
```authentication_configuration=AuthenticationConfiguration(connection_arn='asdf')```
This is how it currently works.

no, current Class name is `ServiceSourceConfigurationAuthenticationConfiguration`

it should be at least 2 or 3 nested packages in order to prevent namespace conflicts.

not just concacetnating names

On top of that word `Configuration` repeats in the name twice.

In this class even three times!

```ServiceSourceConfigurationCodeRepositoryCodeConfigurationCodeConfiguration```

names like this does not make anything easier to read, it's the exact opposite

It’s unlikely that we will take a massive breaking change like this, but you are welcome to open an issue and summarize your suggestion