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

Add API Test Project #117

Open
wants to merge 59 commits into
base: master
Choose a base branch
from
Open

Add API Test Project #117

wants to merge 59 commits into from

Conversation

br-iosb
Copy link
Contributor

@br-iosb br-iosb commented Apr 11, 2022

Add First Postman Collection
Add Documentation
Add automated Pipeline Test

juileetikekar and others added 30 commits January 13, 2022 09:43
-Support for Basic Authentication
Swagger Project path fixed, Swagger Test Project added (#93)
added test project (#94)
test for fixing blob modifier (#95)
Platform Industrie 4.0 changed license to Creative Commons CC BY 4.0
-Support for Basic Authentication
Swagger Project path fixed, Swagger Test Project added (#93)
added test project (#94)
test for fixing blob modifier (#95)
juileetikekar and others added 29 commits February 21, 2022 14:52
Platform Industrie 4.0 changed license to Creative Commons CC BY 4.0
Fix failing checks
appsettings was not copied in build process due to an invalid json schema
standard aspnet config does not work with current use of AasxServerStandardBib Program.cs
app does only run correctly within the build directory
server does not uses same port consistently (sometimes 5000, sometimes port specified in appconfig.json) across different platforms
see https://docs.microsoft.com/de-de/aspnet/core/fundamentals/servers/kestrel/endpoints?view=aspnetcore-6.0
There are two aspnet project, where AasxServerBlazor uses IO.Swagger as library. This leads to inconsistent builds e.g. duplicated appsettings.json.
working directory for server must be within build
cd out of build folder after starting server
@Freezor
Copy link
Contributor

Freezor commented Jun 6, 2024

@br-iosb is this PR still valid? and if so can you rebase and fix the merge issues? I would gladly take a look then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants