You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI does not force tags on a pipeline to be created in the form key:value. The UI also allows pipeline filters to be created which simply match the single-value string that was used to tag a pipeline.
E.g. I can tag a pipeline as database-user-management and create a filter for that tag. The pipeline will be visible in the filtered list.
But with the terraform provider, this is not possible. If I omit the value from the tag there is an error.
If no value is provided a simple filter should be created without a colon using just the key, as is possible in the UI.
Actual Behavior
The execution failed and produced an error:
panic: interface conversion: interface {} is nil, not string
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Create a simple pipeline filter resource which filters only by tag. For example:
Terraform Version
1.4.4
Affected Resource(s)
Please list the resources as a list, for example:
Debug Output
Not available.
Panic Output
panic output
Expected Behavior
The UI does not force tags on a pipeline to be created in the form
key:value
. The UI also allows pipeline filters to be created which simply match the single-value string that was used to tag a pipeline.E.g. I can tag a pipeline as
database-user-management
and create a filter for that tag. The pipeline will be visible in the filtered list.But with the terraform provider, this is not possible. If I omit the
value
from the tag there is an error.If no value is provided a simple filter should be created without a colon using just the key, as is possible in the UI.
Actual Behavior
The execution failed and produced an error:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Important Factoids
No
References
None
The text was updated successfully, but these errors were encountered: