`google_data_pipeline_pipeline`: `state` defaults to `STATE_ACTIVE` despite other enums set in config

[BBBmau]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version & Provider Version(s)

Terraform v1.7.5

• provider registry.terraform.io/hashicorp/google v6.45.0

Affected Resource(s)

google_data_pipeline_pipeline

Terraform Configuration

n/a

Debug Output

No response

Expected Behavior

should be able to set the state to any other type that isn't STATE_ACTIVE

Actual Behavior

reapplies and sets in state as STATE_ACTIVE despite setting it as any other value that isn't STATE_ACTIVE, e.g STATE_PAUSED

Steps to reproduce

No response

Important Factoids

Initial the pipeline is created successfully.

However, when I changed the value of state to STATE_PAUSED then trigger an apply run, the run will show a force replacement of the resource and the apply goes successful as well.

But the state of the pipeline does not change and remains active in the GCP console.

We destroyed and tried to create the pipeline multiple times with different state values STATE_ARCHIVED, STATE_PAUSED, STATE_ACTIVE and STATE_STOPPING, but the pipeline was created every time with active status.

References

Terraform Doc: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/data_pipeline_pipeline

b/436660818

[melinath]

The API field description is confusing:

Required. The state of the pipeline. When the pipeline is created, the state is set to 'PIPELINE_STATE_ACTIVE' by default. State changes can be requested by setting the state to stopping, paused, or resuming. State cannot be changed through pipelines.patch requests.

On the one hand, state changes can be requested - but you can't do it with the patch method. Looking at the available enum values and the API structure, I think that the state is intended to be modified through custom methods:

• https://cloud.google.com/dataflow/docs/reference/data-pipelines/rest/v1/projects.locations.pipelines/run
• https://cloud.google.com/dataflow/docs/reference/data-pipelines/rest/v1/projects.locations.pipelines/stop

We should probably handle this with a desired_state field (and make state output-only). Changing state to output-only would be breaking, so we'd have to do it as part of a major release (possibly the current one?)