-
Notifications
You must be signed in to change notification settings - Fork 189
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
Add support for specifying a custom Logical ID for the AWS::AppSync::GraphQLApi resource #618
base: master
Are you sure you want to change the base?
Conversation
@@ -104,6 +106,6 @@ export class Naming { | |||
} | |||
|
|||
getAuthenticationEmbeddedLamdbaName() { | |||
return `${this.apiName}Authorizer`; | |||
return `${this.config.name}Authorizer`; |
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.
Is this necessary?
Unless I am missing something, we probably could get away with having a
apiLogicalId
that overrides getLogicalId
.
The rest of the logical ids should be safe. i.e. They might be re-created but they are not stateful.
That would simplify everything.
@@ -12,6 +12,7 @@ export type AppSyncConfig = { | |||
pipelineFunctions: Record<string, PipelineFunctionConfig>; | |||
substitutions?: Substitutions; | |||
xrayEnabled?: boolean; | |||
logicalIdPrefix?: string; |
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.
As per my other comment, could this be named apiLogicalId
?
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.
Thank you @manwaring
Could we also add documentation of when and how to use it?
Exploring a possible solution to #617 by supporting a parameter to prefix the
AWS::AppSync::GraphQLApi
Logical ID (instead of only supportingGraphQlApi
)