Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Meta-Issue]: Autoflex General Availability #36815

Closed
breathingdust opened this issue Apr 9, 2024 · 5 comments
Closed

[Meta-Issue]: Autoflex General Availability #36815

breathingdust opened this issue Apr 9, 2024 · 5 comments
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope. flex Pertains to FLatteners and EXpanders. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. provider Pertains to the provider itself, rather than any interaction with AWS.

Comments

@breathingdust
Copy link
Member

Description

Autoflex is a transparent type mapping component which is currently being used in a number of resources and datasources in the provider. This prevents the need for manual creation and maintenance of mapping functions to be required as part of resource implementation.

This is significant step forward in reducing the time it takes to create (and maintain) a resource, so the end goal is for the team to require its usage for new resources to maximize its effect. In order to do this, a number of tasks need to be completed:

Comprehensive contributor documentation

  • How to use Autoflex
  • How to troubleshoot Autoflex
  • How to raise issues related to Autoflex

Improved Tracing/Logging

Currently problems with Autoflex can be difficult to pinpoint without detailed knowledge of the component. Problems with Autoflex should be easy to identify.

Completion of any known Unsupported Types

Policy Change Announcement

  • A clear timeframe for any policy requiring Autoflex's use need to be communicated to the community ahead of the date it goes into affect.
  • This includes any automation/checks required to flag manual flex functions.

Affected Resource(s) and/or Data Source(s)

No response

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

None

@breathingdust breathingdust added the enhancement Requests to existing resources that expand the functionality or scope. label Apr 9, 2024
Copy link

github-actions bot commented Apr 9, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@breathingdust breathingdust added provider Pertains to the provider itself, rather than any interaction with AWS. flex Pertains to FLatteners and EXpanders. labels Apr 9, 2024
@terraform-aws-provider terraform-aws-provider bot added the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Jun 25, 2024
@diofeher
Copy link
Contributor

+1 on that. I've been writing my first TF resource and it seems besides understanding how schema should be used, the other huge part of the work is to understand expanders and flatters

@breathingdust
Copy link
Member Author

Autoflex is now considered GA and is required for use in net-new resources / data-sources. See: #38907

Copy link

github-actions bot commented Sep 5, 2024

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

Copy link

github-actions bot commented Oct 6, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. flex Pertains to FLatteners and EXpanders. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. provider Pertains to the provider itself, rather than any interaction with AWS.
Projects
None yet
Development

No branches or pull requests

3 participants