add /_localstack/info endpoint for basic infos about the instance

[thrau]

Motivation

Several other localstack systems need access to basic information about the running instance beyond the health status. Much like docker info, this new endpoint aims to provide this information.

Example:

{
  "version": "2.3.3.dev:c77b830",
  "edition": "pro",
  "is_license_activated": true,
  "session_id": "1830110c-6e4d-4256-9bc0-9008b8c5b6b9",
  "machine_id": "4256a311839b",
  "system": "linux",
  "is_docker": true,
  "server_time_utc": "2023-10-04T14:59:40",
  "uptime": 120
}

Changes

• Add a /_localstack/info endpoint
• Add two new metadata methods: getting the edition (from files we create in the Dockerfiles), and checking whether license activation has been successful
• Add the edition key also to the health endpoint, since that has long since been requested
• Add the output of info also to the diagnose endpoint

Testing

• You can use the dev run script and call curl -s https://localhost.localstack.cloud:4566/_localstack/info | jq .

[github-actions]

LocalStack Community integration with Pro

       2 files  ±0         2 suites  ±0   1h 18m 7s ⏱️ + 8m 0s
2 242 tests ±0  1 740 ✔️ ±0  502 💤 ±0  0 ❌ ±0 
2 243 runs  ±0  1 740 ✔️ ±0  503 💤 ±0  0 ❌ ±0 

Results for commit 58f835d. ± Comparison against base commit f5adc8f.

♻️ This comment has been updated with latest results.

[coveralls]

coverage: 82.919% (-0.2%) from 83.12% when pulling db3c6f2 on info-endpoint into f5adc8f on master.

[alexrashed]

Nice! This is going to be super-useful when trying to help our users! 🚀

[alexrashed]

nit: Maybe it would make sense to separate the imports here:

• First try to import anything super-stable from ext.
  • return false if it's not possible
• Then try to import the specific method.
  • list a prominent error in this case, because that would mean that this code stopped working because of a refactoring, not because the package is missing

[lukqw]

This is great! Thanks for the addition 🙌