Add a String contains or includes function that can replace the can(regex(..., ...)) pattern

[Gowiem]

Current Terraform Version

0.14.1

Use-cases

The current solution for checking if a string var or local contains a given substring is typically done using can(regex("substring_to_check", var.my_string)) (and there are a number of other ways to do so as well). IMHO, this is pretty unintuitive as it requires using a couple functions and doesn't "read" well.

The end goal of providing a specific function to handle this problem is to provide a cleaner and more concise way to accomplish the same.

Attempted Solutions

As mentioned above, the current solution is typically done with regex and pals. There are many ways to accomplish this.

Proposal

I'm proposing that Terraform provide a native function to handle this instead of the unintuitive ways it's handled now. This can be seen in many programming languages:

1. Golang strings#Contains
2. Ruby String#include?
3. JS string#includes

I believe a new function like contains (problematic because of the Collection contains function?) or includes would solve this problem elegantly. I think this is worth bringing up since this is such common business logic pattern.

References

N/A

[Geartrixy]

Can the pull request from January be reviewed and incorporated in the next release? :)

[scaswell-hirez]

Hashicorp, y'all have been sitting on this one for over a year since the last comment; almost 2 years since the PR was submitted. It solves a very common use case. Please expedite its inclusion into the next release.

[Chinikins]

would love to see this in the next release....

[mward-varonis]

Any plans on including this in an upcoming release?

Thanks!

[crw]

It is very difficult for us to make forward-looking statements, however the linked PR is on the radar for future inclusion.

[bflad]

@crw I believe this was resolved with #33069 introducing the strcontains() function in Terraform 1.5

[crw]

Thanks @bflad, I appreciate the callout.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.