Creating external connection schema is a long-running operation. To check its status, you need to follow the URL that's returned on the location response header after submitting the schema.
Right now, while creating schema, we're not returning any output. In other words, we submit the job, but don't wait until its completion and also don't output the job status URL. This means, that you can't use this command to build a script, because you could end up trying to ingest the content, while the connection is still being provisioned.
I suggest we do two additions:
- introduce a
--wait option, that will wait until the schema is provisioned. We should poll for the job completion status every 60 seconds
- output the job status URL as returned by the
location response header after submitting the job, in case the user wants to check the job status themselves or our polling fails and user will want to check for it manually in an interactive scenario
Both changes aren't breaking and we can introduce them in a minor version
Creating external connection schema is a long-running operation. To check its status, you need to follow the URL that's returned on the
locationresponse header after submitting the schema.Right now, while creating schema, we're not returning any output. In other words, we submit the job, but don't wait until its completion and also don't output the job status URL. This means, that you can't use this command to build a script, because you could end up trying to ingest the content, while the connection is still being provisioned.
I suggest we do two additions:
--waitoption, that will wait until the schema is provisioned. We should poll for the job completion status every 60 secondslocationresponse header after submitting the job, in case the user wants to check the job status themselves or our polling fails and user will want to check for it manually in an interactive scenarioBoth changes aren't breaking and we can introduce them in a minor version