Add /api/v2/config endpoint

[BogdanIrimie]

The topaz console is moving to the v2 config which contains a list of configs. To support this in topaz we are adding /api/v2/config endpoint which returns a list of configs and a flag that says if the configs are editable or not. In the case of topaz they are never editable that is why we set the readOnly flag to true

Sample output of the new endpoint

{
    "readOnly": true,
    "authenticationEnabled": true,
    "configs": [
        {
            "configType": "auto",
            "name": "Topaz Config",
            "address": "https://localhost:4321/api/v2/config",
            "authorizerServiceUrl": "https://localhost:8383",
            "authorizerApiKey": "",
            "directoryServiceUrl": "https://localhost:9393",
            "directoryApiKey": "",
            "directoryTenantId": "",
            "directoryReaderServiceUrl": "https://localhost:9393",
            "directoryWriterServiceUrl": "https://localhost:9393",
            "directoryImporterServiceUrl": "https://localhost:9393",
            "directoryExporterServiceUrl": "https://localhost:9393",
            "directoryModelServiceUrl": "https://localhost:9393"
        }
    ]
}

Request example:

curl 'https://localhost:8080/api/v2/config' \
  -H 'content-type: application/json' \
  --compressed | jq

The API keys are returned only when the user is authenticated or if anonymous auth is enabled.

closes https://github.com/aserto-dev/workspace/issues/576

[github-actions]

Pull Request Test Coverage Report for Build 7888525799

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• -73 of 73 (0.0%) changed or added relevant lines in 5 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.09%) to 37.266%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pkg/app/topaz.go	0	5	0.0%
pkg/app/console.go	0	9	0.0%
pkg/app/handlers/ui.go	0	9	0.0%
pkg/app/handlers/authorizer.go	0	18	0.0%
pkg/app/handlers/config.go	0	32	0.0%

Files with Coverage Reduction	New Missed Lines	%
pkg/app/topaz.go	1	60.73%

Totals
Change from base Build 7819049478:	-0.09%
Covered Lines:	1494
Relevant Lines:	4009

---

💛 - Coveralls

[gimmyxd]

@BogdanIrimie could we create some symmetry between authorizer and directory?

Let me know if this looks good and i can do the same in BFF

AuthorizerServiceURL     string  `json:"authorizerServiceUrl"`
AuthorizerAPIKey         string  `json:"authorizerApiKey"`
DirectoryServiceURL       string  `json:"directoryServiceUrl"`
DirectoryAPIKey          string  `json:"directoryApiKey"`
DirectoryTenantID        string  `json:"directoryTenantId"`
DirectoryReaderServiceURL *string `json:"directoryReaderServiceUrl,omitempty"`
DirectoryWriterServiceURL *string `json:"directoryWriterServiceUrl,omitempty"`
DirectoryModelServiceURL  *string `json:"directoryModelServiceUrl,omitempty"`

[BogdanIrimie]

Sure, the result after the changes is

{
    "readOnly": true,
    "configs": [
        {
            "configType": "auto",
            "name": "Topaz Config",
            "address": "https://localhost:4321/api/v2/config",
            "authorizerServiceUrl": "https://localhost:8383",
            "authorizerApiKey": "",
            "directoryApiKey": "",
            "directoryTenantId": "",
            "directoryReaderServiceUrl": "https://localhost:9393",
            "directoryWriterServiceUrl": "https://localhost:9393",
            "directoryModelServiceUrl": "https://localhost:9393"
        }
    ]
}

[BogdanIrimie]

Added the authenticatedUser flag just so we know if the user was authenticated or not when the call was made. This makes it easy to distinguish between not receiving API keys because there are none or because the users was not authenticated.

[gimmyxd]

This seems to hardcode the Address. I think we need to provide the configured address for the console service here.

[BogdanIrimie]

Updated so we return the console URL e.g.

{
    "readOnly": true,
    "configs": [
        {
            "configType": "auto",
            "name": "Topaz Config",
            "address": "https://localhost:8080/api/v2/config",
            "authorizerServiceUrl": "https://localhost:8383",
            "authorizerApiKey": "",
            "directoryServiceUrl": "https://localhost:9393",
            "directoryApiKey": "",
            "directoryTenantId": "",
            "directoryReaderServiceUrl": "https://localhost:9393",
            "directoryWriterServiceUrl": "https://localhost:9393",
            "directoryImporterServiceUrl": "https://localhost:9393",
            "directoryExporterServiceUrl": "https://localhost:9393",
            "directoryModelServiceUrl": "https://localhost:9393"
        }
    ]
}