-
Notifications
You must be signed in to change notification settings - Fork 23
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
Setup environments after reset of Integration Env. to get ready for the 24.05. E2E tests. #855
Comments
Asked portal team for futher assistance since the app creation process does not work. |
Hi @mkanal / @jzbmw please assist me with the following topics: The app release process is now working. Following new topics came up.
-> Will those be created after app creation? -> Semantic Data Model, BPDM, Dataspace Discovery
ALL ISSUES in this comment have been resolved. |
Currently waiting for: #778 to be able to test successfully. |
E2E environments are up and running. EDC connection is established and working. |
PO acceptance in behalf of @jzbmw. Works as intended. |
As product
I want to re-setup the int environment after reset of portal and bpdm
so that we are able to join the e2e testing phase
Blocked by: eclipse-tractusx/portal-frontend#736, eclipse-tractusx/portal-frontend#704
Links
Acceptance Criteria
Out of Scope
Hints / Details
please note that we started to reset the Integration Env. to get ready for the 24.05. E2E tests.
As a result, access to the portal and connected applications will be extremely limited until the E2E tests begin.
I understand that this may have a significant impact on many of you. To mitigate the inconvenience, we enabled a special support function. If you still need/want to perform actions such as EDC communications (version < 0.7 RC1), test runs, etc. using previously used users (both technical and functional), you can proceed by switching your connector and/or app instances to the following Keycloak token URL:
Please note that this IDP instance is our previous INT Keycloak instance, which is now available under a new endpoint path. All user accounts and service accounts are still accessible with your existing credentials.
The text was updated successfully, but these errors were encountered: