This message was deleted.

Can you share a bit more of your code? I feel you’re running into a typical go issue around closing over a loop variable

here's an example that would make sense:

func SetupPostgres(ctx *pulumi.Context, args *DataArgs, opts ...pulumi.ResourceOption) error {
  var postgresCfg ConfigPostgres
  config.New(ctx, "data").RequireObject("postgres", &postgresCfg)

  for _, instanceCfg := range postgresCfg.Instances {
    err := setupPostgresInstance(ctx, &instanceCfg, args, opts...)
    if err != nil {
      return err
    }
  }

  return nil
}

func setupPostgresInstance(
  ctx *pulumi.Context, cfg *ConfigPostgresInstance, args *DataArgs, opts ...pulumi.ResourceOption,
) error {
  instance := &PostgresInstance{
    Name:         cfg.Name,
    InstanceName: fmt.Sprintf("postgres-%s", cfg.Name),
  }

  instance.pgaPasswordName = fmt.Sprintf("%s-pga", instance.InstanceName)
  instance.pgaPassword, err = random.NewRandomPassword(ctx, instance.pgaPasswordName, &random.RandomPasswordArgs{
    Length:  <http://pulumi.Int|pulumi.Int>(24),
    Special: pulumi.Bool(false),
  }, opts...)
  if err != nil {
    return err
  }

  pgaConfig := instance.pgaPassword.Result.ApplyT(func(pgaPassword string) string {
    // instance here is the last element, not the current
    return instance.preparePgaConfig(pgaCfg.ApiKey, pgaPassword)
  }).(pulumi.StringOutput)

  return nil
}

I believe so - you’re passing a reference to the loop variable itself, so it will change every time the loop iteration will change. The

ApplyT

callback function will not be invoked until it’s ready, and at that point, you’re referring to the last iteration of the loop most likely

thanks, I'll try to rewrite it to avoid pointers