[Bug]: Publish To Environment creates mistyped environment #2050
Description
AL-Go version
8.0
Describe the issue
If you mistype the environment name in the Publish To Environment workflow. The workflow creates an envirnment of that name. An example (I fogot it did this so had deleted the workflow and haven't got the log)
Last night I had to publish to an environment I forgot I was in a Utility repo instead of a customer one and in this repo the FAT environments are custname_FAT1 and custname_FAT2. Having forgot this I typed FAT*. It failed which is correct so I realesed and ran it correctly.
I have then just Merged a PR into main and the CICD workflow kicked off. It has then failed because it tried to deploy to FAT*. When I check Environments in the Repo settings a new Environment has been created called FAT*.
I have seen issue 798 which the user seems to want to deploy to a none existing environment, and they answer to their question was to use the excludeEnvironments setting this won't work in this case as the envinronment isn't known. I've had this where members of my team have caused this issue and then just ignored subqeuent failures.
If this behaviour is needed by some people can there be a setting to not allow undefined environments, as one misspelling can stop all deployment workflows to fail.
Expected behavior
If the environment specified in the PublishToEnvironment form isn't found I would expect it to fail with error Environment Not Found.
No new Environment should be created.
Steps to reproduce
In a repo run Publish To Environment
type in a none existing environment and run
Additional context (logs, screenshots, etc.)
No response