-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Product import with flag --upsert outputs error #203
Comments
This error isn't really an error (or perhaps it is better to say is, the 404 is expected). The You can hide errors (and usage message) with two environment variables
|
I was just trying those env settings and various flags, but I was not able to block the output. Nor was I able to see appropriate exit codes using
The above shows the 404 errors regardless of the env settings. It returns exit status of 0 when products exists or not.
The above returns 409 and exit status of 0 in both cases. The env settings do affect the display of errors (e.g. Error: unknown flag: --foo) and usage (e.g. after a bad param). The use of Attached is a simple products.json file that I used to test. |
@kurtkanaskie and I chatted, #204 will address the exit status when importing API products. @ana-r-goncalves-alb - What is the reason for |
The scenario I was testing was importing an API product that doesn't exist in Apigee yet, while using the |
Hi,
When importing a new API Product using the import command with the --upsert flag, the product gets created in Apigee but I still get the following error:
Is there a way of hiding this error while still getting the API Product data from the response?
Thank you in advance for your time!
The text was updated successfully, but these errors were encountered: