The ServiceVcl returns the service shape before the activation rather then after the activation

[JiriKovar]

Describe what happened

I have noticed that the output property activeVersion of the ServiceVCL contains the previously activated version throughout the Pulumi UP process.

Example:

• I have a ServiceVCL resource and a separate resource that uses its activeVersion for the purpose of triggering update every time the ServiceVCL is updated (in the code below, its the Waf, which utilizes a dynamic provider)
• Some changes to the ServiceVCL are made
• pulumi up is triggered, ServiceVCL resource gets updated and a new version is activated.
• upon running pulumi preview, the changes shows that the activeVersion was only now changed to the currently active one, which should have been reflected in the preceeding pulumi up.

Sample program

const serviceVcl = new fastly.ServiceVcl(
  name,
  {
    defaultTtl: 10,
    backends,
    domains: domains,
    snippets,
    conditions,
    loggingBlobstorages,
    headers,
    requestSettings,
    gzips,
    dictionaries: dictionaries,
    acls,
    dynamicsnippets: [],
  },
  {
    ignoreChanges: ['versionComment', 'dynamicsnippets'],
    import: args.importId ?? '',
  },
);

new Waf(
  `${name}-waf`,
  {
    ...wafConfig,
    serviceId: serviceVcl.id,
    vclVersion: serviceVcl.activeVersion,
  },
  {
    parent: serviceVcl,
  },
);

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

CLI
Version 3.162.0
Go Version go1.24.2
Go Compiler gc

Plugins
KIND NAME VERSION
language nodejs 3.162.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[corymhall]

@JiriKovar could you provide a sample program that we could use to reproduce the issue? Alternatively if you are able to reproduce the issue in Terraform you could also create an issue with the upstream provider https://github.com/fastly/terraform-provider-fastly

[JiriKovar]

No. I have several requests for repros for similar issues with Pulumi. Sorry, but building a repro for every issue we are facing with Pulumi is growing beyon reasonable and thus I cannot help you further. The description is IMHO good enough to test it yourself.

[t0yv0]

Without a repro I can venture a guess - you may try using pulumi up --refresh to match Terraform refresh-by-default. Without --refresh Pulumi does not refresh, and some providers rely on this Terraform behavior for correct operation.

[JiriKovar]

Unfortunatelly we are running refresh as s separate command quite often and it changes nothing. I understand that trying to repro issues based on the description on your end is also time consuming. In that case, let's just wait until someone has time to do that.