Repository navigation
fix(web): stock provider is created with apiBaseUrl so credential material can pin an origin (CL-8426) - #864
Merged
Merged
Conversation
…erial can pin an origin (CL-8426)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The connect step wrote the base URL onto the catalog model provider only. Stock credential resolution pins material to the stock provider's
apiBaseUrl, so Myra's deployment failed every deploy with "has no API base URL; cannot pin an origin" and the first mail trigger retried forever withallocation_not_ready. The stock provider now carries the connected base URL.