-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Support AWS AppFlow: aws_appflow_connector_profile resource #23892
Conversation
Generally, we omit creation + modification times
Required for CustomConnector connections
"name" is only unique to a particular AWS account. To ensure uniqueness of IDs across multiple AWS accounts, we use "arn" instead.
Since these functions are not exported from the service package, we do not generally include the service in these function names
This reverts commit 5918cea. Connector profiles do not appear to support tagging. The following AWS CLI operation errors out: aws appflow tag-resource --resource-arn <profile_arn> --tags KeyName1=string Returns "Invalud input resource arn"
Hi @szemek. Thank you so much for your work on this! We really appreciate your contribution here -- as well as your past PRs upon which it is based (i.e. #18183 + #19543). Thank you also for keeping up with my numerous edits and tweaking the docs as necessary; it's been very helpful in closing things out here. The major edits here revolved around acceptance testing: namely, our inability to reliably perform acceptance tests that rely upon non-AWS resources. As a result, we can only test connector profiles of Limiting ourselves to Redshift: we're able to get some passing acceptance tests! Other changes mostly focused on adding a couple of missing attributes (i.e. config properties for SAPOData or custom connector profiles) -- and resolving build errors resulting from edits. Code NotesContext-Dependent StructsAs with AppFlow flows (#24017), AppFlow connector profiles have certain attributes representing structures with "context-dependent" members. As the underlying types of these structures are undocumented, we are not able to support their use. Credentials are Write-OnlyCredentials set by Once we're green on all checks, I'll confirm the acceptance tests are still passing one last time, and then we can get this merged! |
Acceptance tests passing on latest commit 7238c86: ❯ make testacc TESTS=TestAccAppFlowConnectorProfile PKG=appflow
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/appflow/... -v -count 1 -parallel 20 -run='TestAccAppFlowConnectorProfile' -timeout 180m
=== RUN TestAccAppFlowConnectorProfile_basic
=== PAUSE TestAccAppFlowConnectorProfile_basic
=== RUN TestAccAppFlowConnectorProfile_update
=== PAUSE TestAccAppFlowConnectorProfile_update
=== RUN TestAccAppFlowConnectorProfile_disappears
=== PAUSE TestAccAppFlowConnectorProfile_disappears
=== CONT TestAccAppFlowConnectorProfile_basic
=== CONT TestAccAppFlowConnectorProfile_disappears
=== CONT TestAccAppFlowConnectorProfile_update
--- PASS: TestAccAppFlowConnectorProfile_disappears (219.21s)
--- PASS: TestAccAppFlowConnectorProfile_update (257.46s)
--- PASS: TestAccAppFlowConnectorProfile_basic (259.99s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/appflow 260.049s Merging! 🚀 |
This functionality has been released in v4.14.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Relates #16253