Reverting changes to a revision results in unaware advanced config changes

[corey-prater]

Description

When needing to revert a change on a particular revision we are noticing an issue where some of the advanced configuration yaml files are being reverted to no configuration. The only way we discovered this was to look at the applied revision upon reverting to see what changes were actually made and noticed a couple of yaml files no longer having their configuration. This resulted in things like the envoy proxy no longer functioning as expected.

To reproduce the behavior, here are the steps to help...

1. Navigate to any project in a company
2. Open the Advanced section under the Design area
3. Expand api-gateway-envoy and open the http-filters.yaml file
4. Apply any valid yaml value to the file (this is for demonstration purposes, no need for valid configuration to reproduce)
   • Same can be said about the swagger-aggregator/swager-aggregator.json config
5. Save the changes
6. Navigate to the current revisions history via the revision selection dropdown
7. From the menu icon to the right, select Restore these changes
   • This will apply a new revision in the history
8. From this same revision history, click the View saved changes button to the right of the most recent save.
9. The change comparison tool should now show the Advanced / api-gateway-envoy / http-filters.yaml file is empty and previous configuration is no longer applied.
   • Same can be said about the swagger-aggregator/swager-aggregator.json config should changes have existed previously.

[ThisIsDemetrio]

Hi @corey-prater!

I think this is the intended behavior if you're in a project without the Enhanced Workflow, because the merging from another branch does not include customization in the Advanced section. I found it at the beginning of the merge documentation (check the warning).

It has to do with the fact that - whenever you change the content of a file in the Advanced area - you have to manually save it from the dedicated button below (and you cannot click on the Save configuration button on the sidebar) because it follows a dedicated flow.

This was a limitation of the save strategy on older Console version that have been solved with the enhanced workflow strategy.

If it's not enabled in the project you're using, unfortunately you have to manually update the files back to how it was.

Hope it helps!

[corey-prater]

In our case, the project is configured as an enhanced workflow.