Support 'Name' property in Custom Resource
See original GitHub issueI have been able to create new Schedules using the Custom Resource in a separate stack. The name of the Schedule is created by concatenating the Stack name with the name of the resource. This makes the name rather long and not very good for using as a tag value.
I assumed that I could define the Name property on the custom resource to over ride that behavior. However I got this error when I tried that.
ERROR : Name is not a valid property for a schedule, valid schedule properties are Description, Enforced, Metrics, OverrideStatus, Overwrite, Periods, StopNewInstances, Timezone, UseMaintenaceWindow, ServiceToken, Timeout
Could you please add the ability to override the name of the schedule by specifying the Name property on the Custom Resource? I see that you are getting ready to release a new version soon. Please include this in the upcoming release!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
AWS::CloudFormation::CustomResource
Only one property is defined by AWS for a custom resource: ServiceToken . ... You can specify a custom resource type name up...
Read more >Support 'Name' property in Custom Resource #71 - GitHub
I have been able to create new Schedules using the Custom Resource in a separate stack. The name of the Schedule is created...
Read more >Custom resource request objects - Amazon CloudFormation
In AWS::CloudFormation::CustomResource , all properties are defined by the custom resource provider. There is only one required property: ServiceToken .
Read more >Custom Resource Guide - Chef Software
Declares the properties of the custom resource; Loads current state of properties for existing resources; Defines each action the custom ...
Read more >How to use a Chef custom resource name as a variable?
By default all the custom resources have the name property which you can access new_resource.name. If you need some other property to become ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, In the upcoming release the custom resource has a property named “NoStackPrefix” that suppresses the stack name prefix. The schedule will take the name of the resource without the prefix if the value is set to True Hope this works for you
Fixed in v1.2.0