fix(amplify-category-notifications): remove env name #1440
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remove env name from the resource name in the notification category fix aws-amplify#1372
ghost
assigned 
| @@ -25,7 +21,6 @@ module.exports = { | |||
| console, | |||
| deletePinpointAppForEnv, | |||
| initEnv, | |||
| initEnvPush, | |||
There was a problem hiding this comment.
Why is this removed? I beleive this would break a few things including migration?
There was a problem hiding this comment.
that was an unneeded leftover from last year, we were talking about possibly separating initEnv locally and then push, but that's not the workflow we used.
|
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
remove env name from the resource name in the notification category
in both the amplify-meta.json file and the backend-config.json file
projects configured by the previous versions will be automatically handled without customers' efforts.
fix #1372
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.