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
After getting the tile settings using OM CLI (ex. om -e env.yml staged-config -p p-healthwatch -c >p-healthwatch.yml), pushing the same file to the OpsManager API (ex. om --env env/env.yml configure-product --config p-healthwatch.yml), this would show the Revert link only when applying changes to the BOSH director.
It is due to subnets' GUID not being persisted between API calls. Here are steps to reproduce:
om --env env.yml --trace staged-director-config --no-redact > director-config.yml
om --env env.yml --trace configure-director --config director-config.yml
Checking the API calls made you would notice that the guid subnets property is not set in the update API call.
After getting the tile settings using OM CLI (ex.
om -e env.yml staged-config -p p-healthwatch -c >p-healthwatch.yml
), pushing the same file to the OpsManager API (ex.om --env env/env.yml configure-product --config p-healthwatch.yml
), this would show theRevert
link only when applying changes to the BOSH director.It is due to subnets' GUID not being persisted between API calls. Here are steps to reproduce:
Checking the API calls made you would notice that the guid subnets property is not set in the update API call.
Checking the OM CLI source code: https://github.com/pivotal-cf/om/blob/main/api/director_service.go#L226-L263. It has a custom function to add the GUID for the network.
Last, I have checked the Ops Manager API would accept a payload with a GUID for subnets (https://github.com/pivotal-cf/om/blob/main/api/director_service.go#L226-L263)
The text was updated successfully, but these errors were encountered: