Enable quota name lookup for aws_servicequotas_service_quota

[alexwilcox9]

Description

The data source aws_servicequotas_service_quota allows for either quota_name or quota_code to be used when looking up a quota. This PR aims to bring the same flexibility to the matching resource so users can avoid hard coding quota IDs

Relations

References

Output from Acceptance Testing

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[ewbankkit]

It seems the more natural thing to do here would be to chain the aws_servicequotas_service_quota data source and resource together in configuration:

data "aws_servicequotas_service_quota" "example" {
  quota_name   = "VPCs per Region"
  service_code = "vpc"
}

resource "aws_servicequotas_service_quota" "example" {
  quota_code   = data.aws_servicequotas_service_quota.example.quota_code
  service_code = data.aws_servicequotas_service_quota.example.service_code
  value        = "42"
}

@alexwilcox9 Does this work for you?

[alexwilcox9]

That does work but I thought it might be cleaner to make the data and resource work in the same way rather than having to use both.