aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::DevOpsAgent::PrivateConnection] - [Enhancement] - Add support for ServiceManagedMode.dnsResolution property
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
Other
### Resource name
AWS::DevOpsAgent::PrivateConnection
### Description
The dnsResolution property is available in the AWS DevOps Agent API/CLI for PrivateConnection under ServiceManagedMode, but it is not exposed in the CloudFormation resource AWS::DevOpsAgent::PrivateConnection.
This creates a gap between what can be configured via API/CLI and what is supported through infrastructure as code. We would like to request support for adding the dnsResolution property to the ServiceManagedMode configuration block of the AWS::DevOpsAgent::PrivateConnection CloudFormation resource, so users can manage this setting declaratively.
References:
[1] create-private-connection
https://docs.aws.amazon.com/cli/latest/reference/devops-agent/create-private-connection.html
[2] AWS::DevOpsAgent::PrivateConnection ServiceManagedMode
https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-devopsagent-privateconnection-servicemanagedmode.html
### Other Details
_No response_
Contributor guide
Research direction
Start with the AWS::DevOpsAgent::PrivateConnection resource and its ServiceManagedMode configuration, then compare the AWS CLI create-private-connection reference with the AWS::DevOpsAgent::PrivateConnection ServiceManagedMode documentation linked in the issue. Done means dnsResolution is exposed in the CloudFormation resource so users can configure it declaratively.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100