-
Notifications
You must be signed in to change notification settings - Fork 57
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
CloudFormation console link resource type coverage #139
Comments
100+ resource type support rolling out regionally now Still adding more resource type deeplink support some percent-encoding issues with some characters in some other services' consoles (SNS, SSM, ECR, etc) Also issues when physical resource IDs are dynamic references |
Any ETA? Would be nice! |
Is it also possible to leverage this functionality with Custom Resources? For example adding a link to the Log Group of the Lambda function? |
@gruebel If you are using a Resource Provider, you can add "resourceLink" to the schema, like the AWS implementation does; |
In the mean time before this gets fixed i've created a google chrome extension that adds links to ALB's, Listeners & TargetGroups - https://chrome.google.com/webstore/detail/aws-ui-helper/mphfofmlanhmdaldkcidkpgnnihimadm?hl=en&authuser=0 . If there is a list of resources with link patterns i can add more resources. |
@challapradyumna open source anywhere for contributions? |
2. Scope of request
When CloudFormation provisions resources for you, you can check what it has created via the "Resources" tab on the stack.
The table lists out the Logical ID, Physical ID, Type, Status, etc.
On certain resources, the Physical ID will be a link that takes you to the page within the AWS Console that represents that resource.
One would expect that if the resource is not click-able that it doesn't exist as something viewable within the console, but this is not the case. There doesn't appear to be consistency between which resources are click-able and which ones are not.
Being able to click on the Physical ID and jump to the section of the console that describes that resource makes for quick drill-downs into what you're dealing with when looking at a stack.
3. Expected behavior
Any resource that can be linked to directly within the console should be linked to via CloudFormation.
Resources that don't have a presence within the console or are sub-sections of other resources should continue to behave as-is and not be linked.
4. Suggest specific test cases
The text was updated successfully, but these errors were encountered: