Backup and/or version portal pages

[#1]

Is it possible to back or version portal pages and assets? Alternatively, is it possible to individually or en masse upload portal pages and assets?

[Marsh]

There is no backup or versioning support for the integrated portals directly available via the UI, but there are APIs that could be used to either back up or upload pages and assets. They're in a private alpha stage, and if you're interested in that, consider reaching out through your account executive.

Versioning and backup are stories that we're tracking, and I'd love to know more about why you asked your question. What is the problem you're looking to solve in this case?

[#3]

The problem we're looking to solve is that we would like to version-control all our portal content, or at least back it up on significant milestones such as an SDK release. Without that capability we might not be able to restore a release should we lose, through our error or some data loss event, the version of a portal our 3rd party and internal developers are relying on.

It's not a showstopper at this stage, since we're releasing an SDK to a limited number of developers, and most large and important parts of SDK content, such as OpenAPI specifications, javadoc-derived documentation, and the source code itself are all in repos and can be tagged with release numbers. But we're creating a significant amount of portal content and we'd like to have some way of recreating that, too, in the event something bad happens.

[#4]

I've asked our Apigee admin to ask for early access to APIs for accessing data in portals in New Edge. In addition to backup, we will also need to access app IDs and API keys through an API.