Open theirman opened 2 years ago
Hi @theirman,
I will point out that you also have the option to deploy the application onto the nodes using the Asadmin CLI; Deploying an Application From the Command Line
You can use this in a single script to automate the deployment on your application across all nodes.
I can continue and put your issue into the voting status if you believe your enhancement would still be useful.
Thank you, Alan
Hi @theirman,
To add onto that, we provide a autodeploy
directory;
You can find the settings in Domain > Application Configuration > Auto Deploy Settings
Thank you, Alan
Hi @theirman,
I will point out that you also have the option to deploy the application onto the nodes using the Asadmin CLI; Deploying an Application From the Command Line
You can use this in a single script to automate the deployment on your application across all nodes.
I can continue and put your issue into the voting status if you believe your enhancement would still be useful.
Thank you, Alan
Thank you @AlanRoth for your answer. Unfortunately, I can't launch another script (systemctl, cron) in a docker container containing payara server. And if I launch it in another container according to the "micro-services" architecture, I can't access the asadmin command
Hi @theirman,
To add onto that, we provide a
autodeploy
directory;You can find the settings in Domain > Application Configuration > Auto Deploy Settings
Thank you, Alan
Thank you again @AlanRoth for your answer. I agree with you, Domain > Application Configuration > Autodeploy Settings allows me to define where I drop my war to do domain autodeployment. So, I miss the same tab to specify where to drop my war to do group autodeployment in Deployment groups > {my_group} > Application Configuration > Autodeploy Settings
For all these reasons, as suggested to me by @JamesHillyard here, I make you my request for improvement to see appearing this functionality which will be useful, I think, to the greatest number
Have a nice day Thierry
Hi @theirman,
Thank you for the details. You are right, the feature is not possible for Deployment groups.
I have put your issue onto community voting status, and will be accepted if it is the most voted issue at the end of a month. We encourage you to rally support for your request.
We always encourage community contributions, so if you wish you can submit a PR implementing this enhancement, and we will gladly review it.
Thank you, Alan
2 questions :
Hi @theirman,
Anybody from the community can vote for your enhancement by reacting with a thumbs up on your issue. We will tally up the votes at the end of every month - if your issue has the highest number of votes it will be accepted.
By PR I mean a pull request.
Thank you, Alan
Hello @theirman,
Your enhancement request has been accepted. I have raised an internal issue FISH-7513
containing your enhancement request.
Description
A possible improvement of Payara would be to have an autodeployment folder at the deployment group level in order to deploy the same war on all the nodes of a deployment group
Expected outcome
When I drop a war archive in the autodeployment folder of a deployment group, the war installs on each node of the deployment group
Current outcome
The major drawback, beyond the loss of time, is the lack of automation in our deployment processes
Alternatives
Currently, developers log into the admin console and manually deploy their webservices
Context
I currently have a Payara server on which I have two deployment groups:
The webservice developers currently have to connect to the interface and manually deploy the war. It would be better if they could drop (SCP, SFTP) in the autodeploy folder of the deployment group to automatically deploy the webservice