Idea ID: 2706651

Better deployment management interface

Status : Waiting for Votes
Waiting for Votes
See status update history
over 1 year ago

Deploy between two environments sometimes can be very difficult. For every package that we want to deploy from an environment to another, we must input a lot of data, like the folder to export, environment password.

When we are deploying a few packages, it is a slow process, but when we talk about every package, for example, it is an unproductive work.

Also, when we have firewall security rules that do not allow two environments to communicate with each other, we must export the packages in the first instance, download it and then upload it to the second instance. Then we access the deployment management and we must, again, select every object, one by one, and input more data (password, filename, directory).

Our request is that PPM provides better deployment management, allowing to spend less time in a deployment process.

Some ideas to improve it:

  • Export:
    • Allow setting a global password and path to the objects that will be exported, so the administrator will input less repetitive data and the chance of human errors will get lower. This way, if a particular package doesn't have its password/path specified, PPM will read it from the global parameter;
  • Import:
    • Allow setting a global password and path to the objects that will be imported, so the administrator will input less repetitive data and the chance of human errors will get lower. This way, if a particular package doesn't have its password/path specified, PPM will read it from the global parameter;
    • Allow setting global parameters to the type of imported objects, like the options of replace validations or add missing security groups. It would reduce human errors and make the process easier;
    • A feature to read all objects of a path and then just change the default options if necessary. In export migration action, it is possible to select more than one object to export but, in import, we must select every file, specify every object type that will be imported and then the password and options. If we have a lot of objects to import, it gets very hard to do and it has a lot of probability that something will go wrong in the case of the administrator input the wrong password one time, for example.

Labels:

Request type
  • I'll open this idea for votes, but considering that DpM is not at the top of our Priorities and hasn't been since the Mercury days, I'd rather hope for some DpM expert to show up and tell you how to do everything you've been asking for with some configuration & some magic tokens.

    Thanks,

    Etienne.