Timeline for Google Deployment Manager References not Working as Expected
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 6 at 4:31 | comment | added | seawolf | The entirety of the configuration is included above... there are exactly two files, and they are included in full. After going through this multiple times I do not see anything that should create a circular reference, but I do not know where there might be a nuance I am not understanding. | |
Mar 5 at 12:15 | comment | added | Kapil Sakhare | Check the nested properties in your configuration again, sometimes it may cause circular references which can lead to such unexpected behavior. | |
Mar 5 at 4:38 | comment | added | seawolf |
I included hardcoded-1 to show that the dependency is properly handled when the reference is part of the name of the resource; the only difference between hardcoded-1 and softcoded-3 with respect to the reference is that in softcoded-3 the reference is not in the top-level name property but rather in a nested property further within the object, yet hardcoded-1 works correctly (even with no dependsOn reference, while softcoded-3 does not at all work as expected or documented. The example in the link from Google's docs shows exactly the outcome I expect but am not seeing.
|
|
Mar 5 at 4:34 | comment | added | seawolf |
I believe this reference already exists, in the softcoded-3.metadata.dependsOn.softcoded-1 lines above... is there a different way to indicate this dependence?
|
|
Mar 4 at 10:56 | comment | added | Kapil Sakhare | As per the error the resource softcoded-1 could not be found when trying to resolve the reference in softcoded-3 and also the reference you provided with softcoded-3 should be correctly matched to hardcoded-3. Try adding a dependency on the softcoded-1 resource to the softcoded-3 resource. This will ensure that the softcoded-1 resource is created before the softcoded-3 resource is created, which may help to resolve your issue. | |
Mar 4 at 2:29 | comment | added | seawolf |
Have done. Note closely that the only difference between softcoded-2 and softcoded-3 is the use of the reference, and the reference (exactly the same) is used successfully in hardcoded-3 but just on the top-level name property of the resource instead of on the properties.name nested property.
|
|
Mar 3 at 12:36 | comment | added | Kapil Sakhare | Check your deployment file and verify if all conditions are correctly defined.According to this official doc, You get a validation error when a field in your configuration fails validation, such as if it uses a string value when a boolean is expected. | |
Mar 3 at 0:50 | history | edited | seawolf | CC BY-SA 4.0 |
deleted 31 characters in body
|
Mar 3 at 0:43 | history | asked | seawolf | CC BY-SA 4.0 |