[BZ 970784] After successful bundle deployment, discover new resources

After a successful bundle deployment, initiate resource discovery for all the affected resources. This should ensure that user doesn't have to manually add new resources to their inventory (or force discovery process).
Le 12/09/2014 19:43, jshaughn a écrit :
> Right, so we have a decision to make here. I don't think the delay
> should be agent-wide, and actually, I don't think the discovery delays
> currently defined in the PC configuration have much to do with this use
> case. I think they are in place more to space out work at
> initialization-time and at import time. I could be wrong but I don't
> think they have anything to do with trying to let, say, a new app, get
> picked up and deployed by an AS.
>

I think it is related to the same problem. You create a child resource 
(say a deployment) but you're not sure it will show up (say in the 
Profile service of EAP5) quickly (if it takes several minutes to get 
started)


> It may be the person writing the bundle that knows best what he's doing
> and what may need to happen at deploy-time, but I think it's the
> deployer that may even be the better person. He knows the bundle and he
> knows the target systems. We could certainly add support as far back as
> the bundle recipe itself, and then allow overrides along the way. But
> for now, I think support at the Deployment level would be reasonable.
> So, maybe adding something like BundleDeployment.discoveryDelay (with a
> defined default) and applying it to the resource deployments (it should
> be accessible through BundleResourceDeployment I think). This would not
> cause an API change. It would mean a new wizard field to allow for
> capturing the setting.
>

+1

> I suppose we could even extend a default setting to the plugin
> descriptor on target types but I'd defer that until some undefined future.
>

-1

> If we have something like a 5 minute default people may never even have
> to worry about setting it.

+1