Skip to main content

Onboarding Context

Prerequisites:
  • You will need elevated permissions to perform most of these actions.
  • Check out Authorization & roles for more info.
note

Onboarding a context is necessary when an application is tailored to a specific context, as it helps link the context to the application in our system. However, if an application is global and not context-specific, there's no need to onboard a context.

  1. Find the context id of the context you want to onboard this can be don by selecting a context in the project portal and copying the guid be hind the context in question.

Image

  1. Go to the Fusion Context API swagger page og the environment you want to onboard the context, se env table below.
  2. Navigate to: 
GET/contexts
  1. Use the OData filter with this query id eq ce31b83a-b6cd-4267-89f3-db308edf721e

Image

  1. Copy the externalId and type.id in this case "externalId": "91dd6653-a364-40c7-af26-7af516d66c42" and "id": "ProjectMaster",

Image

  1. Go to the Portal API URL and navigate to
 POST: /api/onboarded-contexts
  1. Fill in the information and click execute. Image
ENVPortal API URLFuion Context API URL
featurehttps://backend-fusion-project-portal-feature.radix.equinor.com/swagger/index.htmlhttps://fusion-s-context-ci.azurewebsites.net/swagger/index.html
testhttps://backend-fusion-project-portal-test.radix.equinor.com/swagger/index.htmlhttps://fusion-s-context-ci.azurewebsites.net/swagger/index.html
prodhttps://backend-fusion-project-portal-prod.radix.equinor.com/swagger/index.htmlhttps://fusion-s-context-fprd.azurewebsites.net/swagger/index.html