there's something a bit strange here which the tests note as part of their workaround, namely the deployment is using the value prior to its override, which makes this feels a bit icky/nondeterministic ie. runtime value changing while being used. the cleaner way would be to override this as the deployment is being constructed in configstack.
there's something a bit strange here which the tests note as part of their workaround, namely the deployment is using the value prior to its override, which makes this feels a bit icky/nondetermi nistic ie. runtime value changing while being used. the cleaner way would be to override this as the deployment is being constructed in configstack.