Shouldn't API proxy deployment fail if a referenced shared flow(s) are NOT available/deployed in the target environment ?

Google Cloud Apigee
1

We are just starting out with the shared flows at our organization.

Just wanted to understand from the experts within the community about the shared flow behavior and its lifecycle w.r.t. to an api proxy.

  1. Shouldn’t API proxy fail at deploy time if a referenced shared flow(s) is NOT available/deployed in the target environment rather than failing at run time ?
  2. Should we not treat a shared flow(s), just like any other environment level configuration (Target Server. KVM, Cache). What would be use case where we should treat it any differently ?
  3. Should we even version the shared flow bundles to manage its lifecycle ?

My questions are more specific from an enterprise customer perspective, as we have plethora of Apigee Edge orgs./envs.

3 Likes
2

Hi @Mudit, It’s true that as of now

#1 You can undeploy a shared flow even if it’s referenced in APIproxies.
#2 You can deploy the APIproxy when there is no shared flow deployed even with validate=true op which is not same for environment/org-entities.
#3 It is always good to maintain versions for shared flows like we do for APIproxies as we keep updating them.

However, if you use the build tools like maven, you should be able to achieve all the above.
I have not tried but shared flows support is already added to the plugin as mentioned here https://community.apigee.com/content/kbentry/37088/maven-plugin-support-for-shared-flows.html

If you think validations are not included, you can raise an issue.
cc @Sai Saran Vaidyanathan @Madhan Sadasivam

I see a value in adding the validations as a part of the product itself. Maybe someone here can add what’s in the pipeline and other possible ways.

3

Hi @Maruti Chand .

Thank you for the response.

I think for now we will have to write something custom to validate sharedflows during the deploy time.

What was the reasoning/logic behind not having the validations for the sharedflows during deployment ?

Will sharedflow validations during deploy time be part of future product enahancement ? If not, we would be more than happy to put in a feature request

4

On item 1 I agree with you. I’ve filed bugs. I expect we’ll correct this behavior or address it somehow.

1 Like
5

Thanks @Carlos Eberhardt appreciate it. Please share the Jira # with @Maruti Chand so that we can follow up with him for this fix.

6

@Maruti Chand I am in the same situation as the OP of this post. Has there been any development in this case where i can check if the referenced shared flows are deployed or not while deploying an apiproxy?

I tried to figure out if i can use maven to overcome this situation but unable to find any solution either.