A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
If done properly, this could have item 355 rolled into it, since that item is asking for very similar things and honestly any implementation of it will likely cover that ask.
Having an offset, would be nice... Create the app, deploy to your pilot, then prod...
Lack of control for pilot/required deployments caused use to home brew custom apps and detection objects and just sync the content so we could control changes that occur on a sync. Having offset deployments would allow us to just trust the automation.
We would need an individual configuration for each product. For example, some products have only one available install deployment, others have a required install deployment, an available install deployment and a required uninstall deployment. For each deployment there are individual (in our case devices) collections.
You could also make this work for the updates, too, with an auto deployment to a set collection, similar to how SCCM upgrades have the Pre-Production Client designation.
My initial thought was for a single deployment to a user collection that takes care of testing but your idea is even better since we could grant access to different users depending on the application.
If done properly, this could have item 355 rolled into it, since that item is asking for very similar things and honestly any implementation of it will likely cover that ask.
This is an awesome idea...
Having an offset, would be nice... Create the app, deploy to your pilot, then prod...
Lack of control for pilot/required deployments caused use to home brew custom apps and detection objects and just sync the content so we could control changes that occur on a sync. Having offset deployments would allow us to just trust the automation.
any eta? ^^
automating this will save the amout of time to sit and deploy manually for every then and now on new releases..
Fantastic idea, this would be incredibly useful! :)
+1
Request from Twitter: https://twitter.com/CraigDevJohnson/status/1379934780855214084
Great Idea
cool idea, i need this :)
we need this
we need this too,
would like this too
We would need an individual configuration for each product. For example, some products have only one available install deployment, others have a required install deployment, an available install deployment and a required uninstall deployment. For each deployment there are individual (in our case devices) collections.
Nic W, wouldn't an ADR achieve this goal already?
You could also make this work for the updates, too, with an auto deployment to a set collection, similar to how SCCM upgrades have the Pre-Production Client designation.
My initial thought was for a single deployment to a user collection that takes care of testing but your idea is even better since we could grant access to different users depending on the application.
Would you want the deploying of the application configurable at each product level?
A phased deployment option would also be useful.
Good idea, we will monitor this to see what other customers up-vote this idea.