[Platform] Move function name validation from resource to platform #3130
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Function name validation was happening only on the
resourceside, when parsing the function information onCreate/Update/Deleterequests.This allowed deploying functions with invalid names via Nuctl - The deployment would eventually fail, but the error message was not as clear as it should be.
This also caused errors when trying to delete the already erroneous function because delete request failed function validation.
Thus, we move the function name validation to the platform, so it will be appplied both when deploying via the dashboard and via nuctl.
Resolves #3045