Replies: 9 comments 5 replies
-
I am getting this issue again...I can't remember I how handled it before. |
Beta Was this translation helpful? Give feedback.
-
Yes I did
…On Fri, Jun 7, 2024, 5:24 PM Kamil Nowinski ***@***.***> wrote:
Did you raise it in GitHub before?
—
Reply to this email directly, view it on GitHub
<#345 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQABJCTLBXBCLVKQV642TTLZGIQJDAVCNFSM6AAAAABI7F4CBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMBXGYYDO>
.
You are receiving this because you modified the open/close state.Message
ID: <Azure-Player/azure.datafactory.
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
We were having the same issue. I just disabled the Incremental option in our Release Task and it finally worked. I'm wondering if the issue may be related to the Get-GlobalParam function or something similar since it makes an API call and we're getting 404 in response with Incremental turned on. |
Beta Was this translation helpful? Give feedback.
-
I fixed things because I had a small error in my config file. But the
error is not very helpful.
…On Wed, Jun 19, 2024, 8:18 PM jsebpi ***@***.***> wrote:
We were having the same issue. I just disabled the Incremental option in
our Release Task and it finally worked.
I'm wondering if the issue may be related to the Get-GlobalParam function
or something similar since it makes an API call and we're getting 404 in
response with Incremental turned on.
—
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQABJCXQQGUATX6X23BUXM3ZIINVRAVCNFSM6AAAAABI7F4CBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMRSHAZTK>
.
You are receiving this because you modified the open/close state.Message
ID: <Azure-Player/azure.datafactory.
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@BigTP25, can you advise what error you've got in your config? |
Beta Was this translation helpful? Give feedback.
-
I'm actually having the same issue & my config file is valid. |
Beta Was this translation helpful? Give feedback.
-
@kamil
I had a small error in the config that was pointing to the wrong resource
group.
…On Fri, Jun 21, 2024, 5:54 AM Kamil Nowinski ***@***.***> wrote:
@BigTP25 <https://github.com/BigTP25>, can you advise what error you've
got in your config?
—
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQABJCQX7XPBI3ZQAIBSY3TZIPZ5RAVCNFSM6AAAAABI7F4CBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMZYGI2DO>
.
You are receiving this because you were mentioned.Message ID:
<Azure-Player/azure.datafactory.
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I don't think so, not for me at least...
…On Thu, Jun 27, 2024, 2:43 PM Kamil Nowinski ***@***.***> wrote:
Hence, there was nothing related to Incremental Deployment feature, is
that correct?
—
Reply to this email directly, view it on GitHub
<#345 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQABJCVAPR5T2HHPUQGHIPLZJRMMHAVCNFSM6AAAAABI7F4CBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJXGU4TE>
.
You are receiving this because you were mentioned.Message ID:
<Azure-Player/azure.datafactory.
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I appreciate the responses. For me, I double checked my configs for the
environment or "stage" I was deploying to and found an issue with the
resource group I was saying a particular resource should reside. I fixed
that and everything deployed fine for me. I mean the 404 does make sense
when I look at it from that POV... but it is kind of a generic error
returned that doesn't point you in any direction. It would be nice if there
was some sort of check on the config value stipulated and what is specified
in the task and returned a better error. But ultimately, for me, it was
user error and I appreciate the hard work and continued support. Thanks for
your help!
…On Thu, Jun 27, 2024, 2:47 PM Kamil Nowinski ***@***.***> wrote:
I can't help when people do not provide enough details allowing me to
reproduce the error scenario. If you still feel you're facing the issue due
to an error in this module - create a new issue and provide enough details.
—
Reply to this email directly, view it on GitHub
<#345 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQABJCXMYTDSCJG6NTQ7MDTZJRM2ZAVCNFSM6AAAAABI7F4CBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJXGYYTI>
.
You are receiving this because you were mentioned.Message ID:
<Azure-Player/azure.datafactory.
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I am getting a 404 error when deploying to another ADF on a different subscription. If the ADF in my UAT environment doesn't exist, it will recreate it but runs into some problems because I have a SHIR and its linked to this UAT ADF environment...so blocker. If the UAT exists, it says "The remote server returned an error: (404) Not Found." Anyone have this problem? Kinda stuck...
Beta Was this translation helpful? Give feedback.
All reactions