This is not the main issue though. Later when I transform the API resource and try to deploy it again, it tries to create a new Logical Id ApidevStage which follows the format, but the stack fails as the it already has a resource for the same api gateway stage but with a different logical Id ApiStage. How to ensure my CFN stack sticks to the same Logical Id for Stage?
Can we explicitly create a stage resource and refer to it inside AWS::Serverless::Api