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

Thanks <@U010UU3CUS2>. Is it only the printing that trips me?

maybe. how are you trying to use it? specifically with “I want to use that name in an env var”

There’s another service that will connect to the internal name of this service.

And I need to configure that other internal’s services environment with something like `API_ENDPOINT=<http://api-vvf3g61k:8080>`

okay, cool…so that is the “what” you want to do, now “HOW” are you planning to do it?

If I set `metadata.name` to `api` for example, I will be able to use ``API_ENDPOINT=<http://api:8080>` and this works.

code / pseudocode is always good :slightly_smiling_face:

But let pulumi autogenerate a name for the service

Maybe my strategy is not pulumi-style :slightly_smiling_face:

`srv_name1 = api_service.metadata.name` what are you doing with `srv_name1` after this?

```serv2_deployment = Deployment(
...
     "spec": {
...
         "containers": [
             {
...
                 "env": [
                     {"name": "API_HOST", "value": "<http://%s>" % srv_name1},
                 ],
...```

and that isn’t working for you, correct?

I get something like `http://&lt;pulumi.output.Output object at 0x10e3fe850&gt;` :slightly_smiling_face:

try something like
```serv2_deployment = Output.all([srv_name1]).apply(lambda s: Deployment("""json here""")) # replace srv_name1 with s[0][0]```

at that point you may be able to reference `api_service.metadata.name` unless you use `srv_name1` elsewhere

<https://gist.github.com/ohlol/330bc4fd062700dde7d8fd15cf3e18ab>

`self.vpc` is a `pulumi_aws.ec2.Vpc` object

if I passed `self.vpc.id` directly the jinja template output would look like your URL

<@U010UU3CUS2>: Now I get `pulumi_kubernetes.apps.v1.Deployment.Deployment object at 0x1132ccc50` instead of `pulumi.output.Output object at 0x10d985050` …

The more explicit you can be the better I can try to help

The environment variable in the Deployment is now set to `<http://pulumi_kubernetes.apps.v1.Deployment.Deployment> object at 0x1132ccc50` instead of `<http://pulumi.output.Output> object at 0x10d985050`