Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hierarchical Approval for Onboarding and Service Design #341

Open
JohnathanBrammall opened this issue Mar 8, 2022 · 1 comment
Open
Labels
Epic refinement needed Further refinement of requirements needed

Comments

@JohnathanBrammall
Copy link

JohnathanBrammall commented Mar 8, 2022

To be confirmed with program directors and policy stakeholders.

APS needs an ability for business program owners to self-serve and manage the teams and services providing their APIs.

A program owner must be able to agree to the terms and responsibilities for using the API gateway and create a namespace and delegate management to others, approve the creation of a namespace for their program that fall under their agreed terms and responsibilities. Namespaces without a program owner must be approved by APS, such offering will be limited to APS' capacity to administer the namespaces.

Under consideration, namespaces without program approval will have to use assigned URLs for deployment to limit the risk of a service appearing as a legitimate service offering by BC Government.

@ikethecoder
Copy link
Member

No longer blocked by Hierarchical Access Management

@ikethecoder ikethecoder added the refinement needed Further refinement of requirements needed label Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic refinement needed Further refinement of requirements needed
Projects
None yet
Development

No branches or pull requests

2 participants