The --environment-name option originally existed for spin deploy, to allow users to choose between Fermyon Platform instances. In the cloud plugin, the only instance of the cloud is, er, the cloud, and the only case for custom environments is for folks within Fermyon working on the cloud. Hiding the option would get a wordy and obscure option out of users' faces; we could retain it for dev-test purposes but document it in the repo rather than in the CLI.
The
--environment-nameoption originally existed forspin deploy, to allow users to choose between Fermyon Platform instances. In the cloud plugin, the only instance of the cloud is, er, the cloud, and the only case for custom environments is for folks within Fermyon working on the cloud. Hiding the option would get a wordy and obscure option out of users' faces; we could retain it for dev-test purposes but document it in the repo rather than in the CLI.