Closed mike-gangl closed 5 months ago
in unity-dev API Gateway, I've configured a 'mock' endpoint called "info." This takes a integration request
there is an integration request mapping template for
application/json
{"statusCode": 200}
and a integration response mapping template:
application/json
{
"statusCode": 200,
"message": "Unity development environment API"
}
Hosted website (portal) (e.g. www.dev.mdps.mcp.nasa.gov) has a default root of "index.html"
/info endpoints have been added to the dev, test, and prod API Gateways.
EX1EKVK33463U in unity-test was deleted as no managment console should be deployed in that environment.
Only remaining issue is the unity-cs cloudfront distribution. We could get around this by simply setting a default endpoint; may or may not matter if it exists or not.
i've spent about 2 hours total on this particular ticket, for time tracking purposes.
Based on https://jaas.gsfc.nasa.gov/servicedesk/customer/portal/2/GSD-3294
Each cloudfront distribution should have a default object, that is, if we point a browser at the cloudfront url, it should default to a specific object.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/DefaultRootObject.html#DefaultRootObjectHowToDefine