I want to generate API and data model java files for my spring boot project through Open Api Generator (not Swagger code generator). http://api.openapi-generator.tech/index.html
This is the yaml file.
https://forge.3gpp.org/rep/sa5/MnS/raw/Rel-16/OpenAPI/provMnS.yaml
Note: yaml file has $ref in schema.
schema:
$ref: '#/components/schemas/NotifyMoiCreation'
I have tried to create through open api online generator but not able to create it. I am giving the yml file in the box but it is stuck at loading. Please help.
Getting this error on dev tool console if I upload the yaml file url.
Getting this error on dev tool console if I upload the yaml file from my local machine and also all the other dependency yaml files are present in the same folder along with provMnS.yaml:
Note : The main provMnS.yaml file has dependency on other yaml files.
$ref: 'comDefs.yaml#/components/schemas/ErrorResponse' etc...
Related
In order to generate client library, I would to get the Quarkus generated openapi yml file at build time.
For now the only way I found to get it is running the server and get it from the /q/openapi endpoint but it is overkill in the process to have to run the server just to have the spec yml file.
This file will be used as input to generate client libs with generators in CI.
You can set the following property:
quarkus.smallrye-openapi.store-schema-directory
in the application.properties of the server
Example:
quarkus.smallrye-openapi.store-schema-directory=target/generated/
will store it relative to your project folder under target/generated.
Both the json and yaml version will be stored.
See https://quarkus.io/guides/openapi-swaggerui#quarkus-smallrye-openapi_quarkus.smallrye-openapi.store-schema-directory
In my release pipeline I am using File Transform option for my web.config.
I have web.config and web.staging.config
File transform is working and changes are applied in web.config but why web.staging.config is still present in the final deployed package.
Am I missing any configuration or this a normal behaviour?
For this issue , with XML file transformation, the web.xxx.config file is required. The transform will be applied when publish web app to web deploy package or publish to server directly per to the configuration.
As stated in the documentation: You need to create a Web Application package with the necessary configuration and transform files.
So if you want to removing all config transforms, as a workaround , you could add a Delete-files task in the end to remove all configuration files. For example:
Source Folder:
$(wwwRoot)\
Contents:
**\*.staging.config
Here is a case with similar issue , you can refer to it for details.
I am working on Bot framework Virtual Assistant Template. There is a deployment folder where .LU files resides. But i created LUIS app in LUIS site and can export LUIS app as JSON format. Currently i am generating .lu file manually. Is there any option that i can generate .lu file using command lines or cli or some thing with help of JSON file that i exported.
Have a look to LUDown tool in BotBuilder tools, and in particular to its refresh method:
LUDown github is here
Refresh is here:
You can use the refresh command to re-generate .lu files from your
LUIS JSON and / or QnAMaker JSON files.
Below is command line to generate .lu from json file
Note: We have to change directory to npm.
C:\Users\local\AppData\Roaming\npm>ludown refresh -i "
I am working through how to automate the build and deploy of my Service Fabric app. Currently I'm working on the package step and while it is creating files within the pkg subfolder it is always creating a folder hierarchy of files, not a true package in a single file. I would swear I've seem a .SFPKG file (or something similarly named) that has everything in one file (a zip maybe?). Is there some way to to create such a file with msbuild?
Here's the command line I'm using currently:
msbuild myservice.sfproj "/p:Configuration=Dev;Platform=AnyCPU" /t:Package /consoleloggerparameters:verbosity=minimal /maxcpucount
I'm concerned about not having a single file because it seems inefficient in sending a new package up to my clusters, and it's harder for me to manage a bunch of files on a build automation server.
I believe you read about the .sfpkg at
https://azure.microsoft.com/documentation/articles/service-fabric-get-started-with-a-local-cluster
Note that internally we do not yet support provisioning a .sfpkg file. This is a feature that will be coming in soon (date TBD). Instead, we upload each file in the application package.
Update (SF 6.1 - April 2018)
Since 6.1 it is possible to create a ZIP file (*.sfpkg) and upload it to an external store. Service Fabric executes a GET operation to download the sfpkg application package. For more infos see https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-package-apps#create-an-sfpkg
NOTE: This only works with external provisioning, the Azure image store still doesn't support sfpkg files.
I am trying to automate deployments of a particular project and a bit lost as to who to handle config file as well as user assets.
(Application is based on Zend Framework based btw).
Main application folder is structured as follows:
./app
./config.ini <----- config file
./modules
./controllers
./models
./views
./libs
./public
That config file is where all the configs are stored.
So 'app' folder contains whole bunch of code in PHP and 'public' contains whole bunch of code in JavaScript, HTML/CSS and stuff like that(web accessible basically).
If I follow Capistrano's model, where each package is expanded into it's own folder that is then symlinked to, how do I handle that config.ini file?
What about all the user content that is uploaded into ./public folder?
Thanks!
The Capistrano approach to this is to have a structure like this on your remote server:
releases/
20100901172311/
20101001101232/
[...]
current/ (symlink to current release)
shared/
in the shared directory you include your config file and any user generated content (e.g. shared/files). Then on each deployment, once you've checked out the code you automatically create symlinks from the checkout into your relevant shared directories. E.g.:
releases/20101001101232/public/files -> shared/files
releases/20101001101232/application/configs/config.ini -> shared/config.ini
that way, when a user uploads a file to public/files it is actually being stored in shared/files.