-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Data source for aws_service_discovery_dns_namespace #6856
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @saravanan30erd! This looks great, I'd just swap to using constants for validation on the dns_type
attribute
$ make testacc TEST=./aws TESTARGS='-run=TestAccDataSourceAWSServiceDiscoveryDnsNamespace_basic' |
@mbfrahry -- Looks like this one is ready to go. Could you give it another review please? This data source will make my life so much easier! :) |
@bflad Can we push this? anything I need to do from my end? |
Hello, |
Great work @saravanan30erd 👏(I believe there is now a button to request a new review). Hi @mbfrahry 👋 |
When can we expect a merge of this? |
Hello, what is the status of this, please? Is this still being developed on? |
Notification of Recent and Upcoming Changes to ContributionsThank you for this contribution! There have been a few recent development changes that affect this pull request. We apologize for the inconvenience, especially if there have been long review delays up until now. Please note that this is automated message from an unmonitored account. See the FAQ for additional information on the maintainer team and review prioritization. If you are unable to complete these updates, please leave a comment for the community and maintainers so someone can potentially continue the work. The maintainers will encourage other contributors to use the existing contribution as the base for additional changes as appropriate. Otherwise, contributions that do not receive updated code or comments from the original contributor may be closed in the future so the maintainers can focus on active items. For the most up to date information about Terraform AWS Provider development, see the Contributing Guide. Additional technical debt changes can be tracked with the As part of updating a pull request with these changes, the most current unit testing and linting will run. These may report issues that were not previously reported. Action Required: Terraform 0.12 SyntaxReference: #8950 Version 3 and later of the Terraform AWS Provider, which all existing contributions would potentially be added, only supports Terraform 0.12 and later. Certain syntax elements of Terraform 0.11 and earlier show deprecation warnings during runs with Terraform 0.12. Documentation and test configurations, such as those including deprecated string interpolations ( Action Required: Terraform Plugin SDK Version 2Reference: #14551 The Terraform AWS Provider has been upgraded to the latest version of the Terraform Plugin SDK. Generally, most changes to contributions should only involve updating Go import paths in source code files. Please see the referenced issue for additional information. Action Required: Removal of website/aws.erb FileReference: #14712 Any changes to the Upcoming Change of Git Branch NamingReference: #14292 Development environments will need their upstream Git branch updated from Upcoming Change of GitHub OrganizationReference: #14715 This repository will be migrating from https://github.com/terraform-providers/terraform-provider-aws to https://github.com/hashicorp/terraform-provider-aws. No practitioner or developer action is anticipated and most GitHub functionality will automatically redirect to the new location. Go import paths including |
@saravanan30erd Thanks for the contribution and apologies for the delay in responding. |
@ewbankkit sure, I will rename the attribute and update you. |
8687530
to
c26dfaf
Compare
@ewbankkit I renamed the attr |
Original submission on this was December 2018?? holy cow. Talk about contributor purgatory. I cannot believe the author stuck with it as long as they did. ping @ewbankkit Is there no way for this to see daylight? |
@anGie44 please check this PR |
Output of acceptance tests (Commercial):
Output of acceptance tests (Gov Cloud):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi again @saravanan30erd , thank you for this PR! Overall looked great 👍 Major thing was getting the PR aligned with new conventions used in the provider as we've migrated over to the V2 of the terraform plugin SDK. Plan to get this into the upcoming release later this week.
Output of acceptance tests:
|
huzzah! |
This has been released in version 3.42.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 for triage. Thanks! |
Do we have documentation on how to use this? data "aws_service_discovery_service" "controller" { error: The provider hashicorp/aws does not support data source "aws_service_discovery_service" |
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. |
Fixes #6384
Output from acceptance testing: