This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
How can we be 100% sure that a customised Dev Portal will not be
invalidated / broken when a customer moves from 16.01 to 16.04? Is there
a sequence of steps / analysis that I can apply to protect against this?
What difference - if any - in auditing / logging capability between
these methods? How granular is the logging around access to KVM via
Management APIs - e.g. in case of a key change actions? Does audit
logging differ by user type?
Interesting issues associated w/APIs and their productisation.
Transformation from project > program > platform/products causes
disruption far beyond IT. Projects and Programs have start and end-date,
defined scope, fixed objectives, budget codes etc...
@Alexander Schamne - see this post for creation of Private Community
within http://community.apigee.com. @Mike Malloy will be able to give
you the necessary privileges to set up your developers.