[FEATURE] Managing API Credentials for Calling REST APIs of SAP Authorization and Trust Management Service

SAP / terraform-provider-btp

Terraform provider for SAP BTP

https://registry.terraform.io/providers/SAP/btp/latest

Apache License 2.0

83 stars 17 forks source link

[FEATURE] Managing API Credentials for Calling REST APIs of SAP Authorization and Trust Management Service #689

Closed CHERIANS closed 1 month ago

CHERIANS commented 8 months ago

BTP CLI Server supports Managing API Credentials for Calling REST APIs of SAP Authorization and Trust Management Service. Implement support for

[ ] Create API credentials
[ ] Show all API credentials
[ ] Show details about specific API credentials
[ ] Delete API credentials

lechnerc77 commented 8 months ago

SAP-internal: Dependency to https://jira.tools.sap/browse/XSUAA-4128 for Swagger file needed for model generation

lechnerc77 commented 6 months ago

Update: The Swagger file is now available ( SAP Internal access only: https://xsuaa-provisioning-sb.cf.stagingaws.hanavlab.ondemand.com/swagger-ui/index.html?urls.primaryName=Platform%20API) containing the schema information.

The resource for the API credentials and especially the models used for the interaction with the CLI backend can now be generated

diya-dhan commented 6 months ago

If after navigating to the above mentioned link, the below page opens up

The right page can be found by choosing Platform API from the Select a definition dropdown.

vipinvkmenon commented 4 months ago

SAP-Internal: Dependency to https://jira.tools.sap/browse/XSUAA-4315 to be resolved

sdischer-sap commented 2 months ago

@CHERIANS Do we have a timeline for that feature to be released? Having this would be highly beneficial for the btp crossplane provider on our end.

vipinvkmenon commented 2 months ago

Dependency on https://jira.tools.sap/browse/XSUAA-4398

v0lkc commented 2 months ago

Do you have any objections if we start implementing this as beta resource and don't wait for XSUAA-4398 to be resolved? Meaning the code would make it to the repository, but the resource itself would not become active/visible to end users for the time being.

lechnerc77 commented 2 months ago

@v0lkc The implementation is already going on. But imho it makes no sense to push a resource that has known errors into a release even as beta. Especially as no external customer up to now has requested this feature.