[FEATURE] Add support for OpenSearch Action Groups

[rossmpersonal]

Is your feature request related to a problem?

I'm always frustrated when when I try to create OpenSearch action groups using the OpenSearch Terraform provider but discover that the provider does not support creating OpenSearch action groups.

What solution would you like?

I would like for the provider to support creating OpenSearch action groups. Specifically, I envisioned that a new resource type opensearch_action_group, which represents an OpenSearch action group, will be created. However, this may not be the best solution. I am open to any solution that solves this problem.

What alternatives have you considered?

I have considered using the REST API but that would not be applying the IaC philosophy. I have considered doing this in the OpenSearch Dashboards web-based GUI but that is not scalable and can't be automated.

Do you have any additional context?

None

[prudhvigodithi]

[Untriage]
Hey @rossmpersonal thanks for opening this enhancement request, if you are open can you please contribute this new feature to the provider?
Thank you

[rossmpersonal]

[Untriage] Hey @rossmpersonal thanks for opening this enhancement request, if you are open can you please contribute this new feature to the provider? Thank you

I do not have the time, resources, or expertise to do this.

In addition, my employer pays lots of $$$$ to use AWS OpenSearch Service, lots of $$$$ for top-tier AWS Enterprise Support, and lots of $$$$ for top-tier AWS Enterprise Professional Services. As a result, there is absolutely no reason, we should have to commit our own time, resources, and expertise to get a half-working provider.

[prudhvigodithi]

Hey @rossmpersonal please note this OpenSearch provider is a community-driven open-source initiative part of the open source OpenSearch community contributed by multiple individual folks.

[rossmpersonal]

I know but it is owned by AWS, supported by AWS, sponsored by AWS, and funded by AWS.

…

On Wed, Dec 20, 2023, at 4:51 PM, Prudhvi Godithi wrote: Hey @rossmpersonal <https://github.com/rossmpersonal> please note this OpenSearch provider is a community-driven open-source initiative part of the open source OpenSearch community contributed by multiple individual folks. — Reply to this email directly, view it on GitHub <#134 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANZC2IL4CGTQ3B7OGZWQ6W3YKNMWZAVCNFSM6AAAAABARZD2DWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGE4TANZTGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dblock]

Hi @rossmpersonal and @prudhvigodithi! I'll try and do my best to address some of this.

my employer pays lots of $$$$ to use AWS OpenSearch Service, lots of $$$$ for top-tier AWS Enterprise Support, and lots of $$$$ for top-tier AWS Enterprise Professional Services

You are absolutely right and you are correct that AWS supports Amazon OpenSearch, which is based on OpenSearch Project. You should totally be requesting this feature to be built by someone at Amazon, but this is just not the best place to ask, simply because 2/4 maintainers of this project here don't even work at Amazon (see MAINTAINERS.md).

Would you like help locating the right people at AWS to talk about this or do you want to talk to your existing support contact about this feature? I can help, I am dblock at amazon com, feel free to email me, cc-ing your rep.

there is absolutely no reason, we should have to commit our own time, resources, and expertise to get a half-working provider

Putting my non-Amazon hat, I always consider the possibility to contribute to open source as an opportunity. It helps me learn and improve my skills, and it's a way to contribute back. I am open source by default. The main reason to commit my time to an open source project is to accomplish my own, selfish, business's goals, faster. Thus, I do appreciate any time that you may or may not have to contribute, including opening this feature request. Thank you.

[rossmpersonal]

I don't intend to be disrespectful and I am sorry if I came off that way. Thank you for your advice about how to ask. I like and use open source software too. However, given the specific circumstances of this specific situation, I don't think my option option should be developing and contributing the feature myself. I appreciate the opportunity though.

…

On Wed, Dec 20, 2023, at 6:00 PM, Daniel (dB.) Doubrovkine wrote: Hi @rossmpersonal <https://github.com/rossmpersonal> and @prudhvigodithi <https://github.com/prudhvigodithi>! I'll try and do my best to address some of this. > my employer pays lots of $$$$ to use AWS OpenSearch Service, lots of $$$$ for top-tier AWS Enterprise Support, and lots of $$$$ for top-tier AWS Enterprise Professional Services > You are absolutely right and you are correct that AWS supports Amazon OpenSearch, which is based on OpenSearch Project. You should totally be requesting this feature to be built by someone at Amazon, but this is just not the best place to ask, simply because 2/4 maintainers of this project here don't even work at Amazon (see MAINTAINERS.md <https://github.com/opensearch-project/terraform-provider-opensearch/blob/main/MAINTAINERS.md>). Would you like help locating the right people at AWS to talk about this or do you want to talk to your existing support contact about this feature? I can help, I am dblock at amazon com, feel free to email me, cc-ing your rep. > there is absolutely no reason, we should have to commit our own time, resources, and expertise to get a half-working provider > Putting my non-Amazon hat, I always consider the possibility to contribute to open source as an opportunity. It helps me learn and improve my skills, and it's a way to contribute back. I am open source by default <https://code.dblock.org/2015/02/09/becoming-open-source-by-default.html>. The main reason to commit my time to an open source project is to accomplish my own, selfish, business's goals. Thus, I do appreciate any time that you may or may not have to contribute, including opening this feature request. Thank you. — Reply to this email directly, view it on GitHub <#134 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANZC2IJHEEECMO4ZHFUHJ3LYKNUYXAVCNFSM6AAAAABARZD2DWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGI2TGMBXHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>