feature: AWS Config Catalog Plugin fieldsTransform for Any Field

[Chris-Lee-Ca]

🔖 Feature description

The fields currently supported by the fieldsTransform function are hardcoded, as seen here. This implementation lacks support for certain fields, such as title and tag, which could be very useful. Additionally, my company has custom fields that we would like to process using the fieldsTransform function.

It would be beneficial if the fieldsTransform function could support transformations for any field, making it more flexible and accommodating for additional use cases.

🎤 Context

Proposed Solutions:

1. Extension Point: Introduce an extension point so developers can add support for missing fields and implement custom transformation logic as needed.
2. Default Transformation: For all fields not currently covered by the hardcoded implementation, apply a default transformation logic (e.g., the basic fieldsTransform function). Developers could then use expressions to handle most cases.

✌️ Possible Implementation

No response

[niallthomson]

Hi @Chris-Lee-Ca thanks for raising the issue. We did consider adding a mechanism where you can produce your own "partial" resource that gets merged, allow you to basically override any field. The initial concern was that this could make it easier to break the entity that was produced.

Does this sound like it would be useful?

[Chris-Lee-Ca]

Yeah, it sounds really useful. I'm not too worried about it breaking the entity. Either way, we will do enough testing before pushing the changes to production

[niallthomson]

I'll try to resurrect the implementation next month.