[Fleet] Without clicking on upgrade package button, Integration gets updated by itself on just adding it to a policy.

[dikshachauhan-qasource]

Kibana version:
7.13 BC4 Kibana Cloud QA environment

Host OS and Browser version:
Integrations, All

Preconditions

1. 7.13 BC4 Kibana Cloud QA environment should be available.

Kibana version: 7.13 BC4
BUILD 40749
COMMIT 5a6bad454ffe263aafed54cbd3f764253694bf37
Artifact link: https://staging.elastic.co/7.13.0-5c4bc719/summary-7.13.0.html

2. Managed host should be available under Agents tab.

Steps to reproduce:

1. Login to Kibana cloud environment.
2. Go to Integrations tab and click on Nginx integration
3. Use below API to see the indicator next to the version number that the package is outdated.
   curl -X POST -u $USER:$PASSWORD http://$KIBANA_URL:$KIBANA_PORT/api/fleet/epm/packages/nginx-0.3.7 -H 'kbn-xsrf: xyz' -H "Content-Type: application/json" -d '{"force": true}'
4. Navigate to the Settings Tab and verify that you see a button to upgrade the package.
5. Without clicking on it, add Nginx integration to any policy.
6. Navigate back to settings page.
7. Observe,

Reference Link:
#93712

Actual Result:

• Adding integration to a policy makes it upgrade to latest package version available.
• Without clicking on button to upgrade the package, Integration gets updated by itself on just adding it to a policy.

Screenshots:

Expected result:
Package should be updated to latest package version available after clicking on button to upgrade the package.

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[dikshachauhan-qasource]

@manishgupta-qasource Please review

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[EricDavisX]

@jen-huang I moved this from "integrations' repo, believe it is on Fleet team Kibana side to review. I don't think we've changed the spec here, unless I'm out of date. It is interesting... and may end up as a 'good thing' that it is doing? Tagging @mostlyjason to confirm the spec / intention around it too, we may just need to update test steps and documentation?

[ruflin]

This sounds indeed like a bug and I would argue is not the expected behaviour.

[jen-huang]

Yep it's a bug, due to the different code path that the two install paths take :(