You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 7.16, Fleet will be auto upgrading the Synthetics package on fleet startup, but not auto upgrading existing synthetics integration policies. This means that new versions of the UI need to be able to support legacy policy version.
To mitigate this, the Fleet team will provide a way for policies to be upgraded to the latest version when edited. This ensures that the new UI elements in new versions will be able to be utilized for legacy policy versions and simultaneously enable those policies to upgrade to the latest version.
The Fleet team has provided a POC that we need to validate for this flow #114914. Once validated, we will need to fully integrate with this POC to ensure that legacy policy versions can work with the newest version of the UI.
The text was updated successfully, but these errors were encountered:
dominiqueclarke
changed the title
[Uptime] Update Synthetics Integration UI to support legacy
[Uptime] Update Synthetics Integration UI to support legacy policy versions
Oct 14, 2021
In 7.16, Fleet will be auto upgrading the Synthetics package on fleet startup, but not auto upgrading existing synthetics integration policies. This means that new versions of the UI need to be able to support legacy policy version.
To mitigate this, the Fleet team will provide a way for policies to be upgraded to the latest version when edited. This ensures that the new UI elements in new versions will be able to be utilized for legacy policy versions and simultaneously enable those policies to upgrade to the latest version.
The Fleet team has provided a POC that we need to validate for this flow #114914. Once validated, we will need to fully integrate with this POC to ensure that legacy policy versions can work with the newest version of the UI.
The text was updated successfully, but these errors were encountered: